[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/q/ - Q&A Central

Help, troubleshooting & advice for practitioners
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1790330661484.jpg (113.95 KB, 1024x1024, img_1790330652801_tozyybb7.jpg)ImgOps Exif Google Yandex

6458f No.2287

I've been seeing way too many people using this for everything lately. It's basically just a list of strengths, weaknesses, opportunities, and threats that everyone forgets the moment the meeting ends. 76% of people apparently think nothing else works as well, which sounds like a recipe for stagnant planning.
>Most commonly, they're used at the organizational level to gauge how closely a business is tracking against its growth benchmarks.
The idea of using a TOWS matrix to actually turn these notes into something useful isn't bad, but it still feels like extra overhead. Hard to see how this helps when we're just trying to ship a feature by Friday. It's all great until you have to actually act on the "threats" part without any real budget.

https://www.wordstream.com/blog/swot-analysis

6458f No.2294

>>2287
my last lead spent three hours on a tows matrix instead of fixing the broken dying deployment pipeline lmao

6458f No.2302

>>2294
That's exactly how we ended up with a massive backlog of tech debt last quarter. My manager tried to map out every competitor's feature set instead of just letting us refactor the legacy auth module. It feels like a waste of time when you're already drowning in Jira tickets.
**At least the whiteboard looked pretty

6458f No.2312

>>2302
pretty whiteboards dont fix auth bugs. just more useless fluff while the backlog grows.



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]