8 ms·
So often in our business, there are few that understand the whole picture of your problem area. Inviting too much critique results in uninformed objections or r
by JoeAltmaier 6y ago
So often in our business, there are few that understand the whole picture of your problem area. Inviting too much critique results in uninformed objections or redundant suggestions that have already been considered and rejected.
The person who has been charged with a task, should have authority to carry it out as best they see fit. Ok, after folks have a chance to review. But letting somebody gate-keep results in stagnation and no progress.
- rubyfan 6y agoWe’re attempting to undergo a culture and operating model change shifting from gate keeping to focus on outcomes. Please wish us luck. I work at a company that has a management team that historically thinks they need to prioritize initiatives for the organization. A little over a year ago we had a conversation with the management team and explained we would like them to focus on outcomes instead of telling us specifically what to do. It didn’t go over well, they basically ignored the entire conversation and told us what to do. We are one year later and now undergoing a shift to focusing the organization on outcomes using OKRs and spotify style agile. People are starting to get it now and we’re having a lot of discussions with the very same leaders on a more individual basis which I think helps. One thing is for certain, people (and culture) are hard to change.
- musingsole 6y ago>The person who has been charged with a task, should have authority to carry it out as best they see fit. That requires specifically assigning someone the task and authority. This is the part most orgs fail on because to accept ownership is to take on risk. Organizations tend to focus on mitigating risk, and so it becomes increasingly difficult to actually have a person designated as responsible for the thing.
- p_l 6y agoexactly. Sometimes it's even worse: "Everyone needs to own the tickets" quite quickly shows that you own the responsibility and blame, but none of authority.
- qznc 6y ago...and if someone naive enough steps up to take responsibility, they don't provide enough authority/resources to achieve the task. This is how organizations destroy autonomy in their employees.
- hashkb 6y agoThis can be by design, so your risk takers always fail, and thus you can say you encourage risk takers but always have cause to fire them, resulting in a team of sycophants with a "culture of autonomy".
- xondono 6y agoThis. I think this is the most common problem in the tech world, and it’s source it’s on hiring. When I hire someone to do a job, I don’t want to tell them how to do it. I want them to figure it out, and ask for help if they need it. For some reason, that’s not how most people work. A lot of them expect you to tell them how, but they will refuse to ask for help until too late. When I was on the other side, the opposite was true too, I has bosses that expected me to do things their way, even if I could demonstrate that there were better. So far my only weapon against this has been to be very selective while hiring.
- deleted 6y ago[deleted]
- gregmac 6y ago> I has bosses that expected me to do things their way This is a reason you need to learn to manage up. I'm pretty clear that I'm oriented around the final objective: I don't want to be told how to do something (though I'm happy to collaborate and listen to suggestions). If someone starts telling me the "how" before the "what" and "why" I interrupt and steer the conversation there first. If you really want to be telling someone only the "how" I'm not the right person to employ, and I'm clear about this early on. The very few times I've got in trouble with this there's been some hidden objective or constraint I wasn't made aware of, and the discussion I have afterwards is that is not compatible with my way of working. This has always resolved successfully and I've never had this issue with someone more than once.
- xondono 6y ago> The very few times I've got in trouble with this there's been some hidden objective or constraint I wasn't made aware of, and the discussion I have afterwards is that is not compatible with my way of working. I’ve had this, but working in hardware development, this things are big problems. I have to admit though, and in those situations the main problem was conveying to the manager (who tends to be an experienced engineer) that they’ve messed up and the specifications they’ve agreed to are physically impossible to construct.
- 6y ago
- WC3w6pXxgGd 6y agoThis is called bike-shedding, and I see it every day at work.