Expectations are set not only for employee, but for employer also. It’s easy to ignore dealing with simple jobs, but very important not to forget while working with knowledge workers. Why? They are less dependent on you and looking for win/win situations is always more fun.
Still thinking how to organize your work? Think no more, answer is obvious.
The problem is that by creating bureaucracies, we put civil servants in a position to make decisions based on abstract and theoretical matters, with the illusion that they will be making them in a rational, accountable way.
Nassim Nicholas Taleb – Antifragile
When you don’t have metrics and measured capacity it’s very easy to miss the point when you need to throw away your PoC and introduce changes into architecture, technology, backlog.
But don’t do it without
- telling what you delegate
- identifying constraints/limits/waterline
- knowing what do you want to achieve
- setting principles
- providing information
Otherwise involved people will
- have tons of meetings to verify options
- involve even more people
- start gathering information _they_ think is needed
Hints from amateur Product Manager. 2 steps needed before taking actions
- Understand how value is created and for whom
- Figure out dependencies
- Solve bottlenecks
- Discard non-value things
What expert would do?