Latest news about Bitcoin and all cryptocurrencies. Your daily crypto news habit.
Problem solvers are best suited to solving problems. They come up with solutions, they soundboard them off each other and then they converge on what seems like the most viable, feasible and desirable solution based on the information that they have.
Problem solvers in the software world include but are not limited to:
- Software & DevOps Engineers
- UI/UX Designers
- Product Managers
- Data Folk
Give them context and Iâd betâââwith a little savviness in the team and close collaborationâââ99 times out of a 100, theyâll come up with a fantastic solution to the problem framed based on the context they have around the problem to be solved.
And, the times they donât come up with a fantastic solution, itâs likely that theyâve got 2 or 3 other solutions that they didnât end up choosing that are likely to solve the problem, itâs just that they plumped for something else. Itâs also highly likely that plumping for that âsomething elseâ isnât an irreversible decision so some harm, but not major harm done.
That all sounds quite easy then if youâre accountable for such a problem being solved, right? Get a team together, frame the problem and then give them autonomy and ownership. Think about the next problem to be solved and then rinse and repeat.
And it is easyâââbut the baffling thing is that, again, the vast majority of those accountable for problems being solved donât do thisâââthey put the problem solvers far, far away from the actual problem being solved. They do things like:
- adding in project and programme managers
- adding in business analysts and quality assurance engineers
- creating business requirement documentation and throwing that over the fence
- sending solutions over email or inputting them into tools like Jira with no context of the actual problem being solved
- telling them of an area to âexploreâ then giving them a deadline and a vanity metric
- bringing them in for status meetings that are then tactically used to influence the solution and muddy the context waters
âŠand every time that happens, you get outcomes like the ones depicted in Jeff Gothelfâs blog on the pitfalls of âprojectsâ where prescriptive tasks are handed down like Moses on the mountain; and the problem solvers are so far removed from the actual problem to be solved that they may as well be freelancers working remotely across 9 different timezones.
Hey team, hereâs the solution to the problem I may or may not have full context of.
Next time you have a problem to solve:
- assemble a team
- provide as much context as you can
- set some guardrails such as time-boxing
- get out of the way
âŠand see the difference it makes.
If you follow Dan Pink, youâd know that mastery and purpose are critical to the right outcomes being derived but so too is autonomy.
Without autonomy, youâve got yourself a bunch of lemmings that will trudge off the edge of a cliffâââand they wonât be coming back.
Move the problem solvers closer to the problem to be solved was originally published in Hacker Noon on Medium, where people are continuing the conversation by highlighting and responding to this story.
Disclaimer
The views and opinions expressed in this article are solely those of the authors and do not reflect the views of Bitcoin Insider. Every investment and trading move involves risk - this is especially true for cryptocurrencies given their volatility. We strongly advise our readers to conduct their own research when making a decision.