Hacker News Reader

Not at L6. Scarface is right, most of the time the org just knows something is wrong and they don’t know what it is exactly or how to fix it. Sometimes they don’t even know something is very wrong, while working on a defining problem 1 the L6 also identifies related problem 2 the org thought was minor but is actually major.

None of this is specified, there are no specs to execute up front. Much of it is defining the spec yourself and collaborating with the rest of the org to find out if other people agree with the spec.

You’re missing that it’s:

- implementing the spec for an existing spec (L4)

- creating the spec for a prescribed product (L5)

- recognizing the need for the product in the first place and advocating to make it happen(L6)

Each level feeds the one below it.

At L6, the problem isn’t defined. They just know something is wrong.

If the company is saying “your job is to find problems and solve them,” you’re still doing what the company is telling you what to do. I’m just saying that if a company wants me to do something, they better accurately define the position (and compensate appropriately).