Latest news about Bitcoin and all cryptocurrencies. Your daily crypto news habit.
You’ve got roadmaps.Epics and stories.UX and Visual designs.Design documents.Technical requirements documents.Database designs.High-level milestones.
You’ve done a lot of work to make sure your developers know what you want them to code.But never forget, when your developer sits down to code, they are in control.
You may give them the requirements, but they will decide if, how and when to code them.
Don’t believe me?
* Have you ever seen parts of the story ignored which they felt were stupid or pointless?
* Have you ever seen design changes magically appear in production which they feel are an improvement?
* Have you ever seen QA send back bugs that the programmer didn’t test for because “no one will ever actually use that button”?
* Have you ever found yourself trying to nudge forward a project that was stuck-in-the-mud because the programmer thought it was a dumb idea?
I’ve seen all of this and more.
Why am I telling you this?Managers have a habit of forgetting how much we depend on our team’s motivation. When we forget, sometimes we fall into thinking…
* This is the job I pay them for, so they should just do it.
* The spec has all the details, they just need to implement it.
* They shouldn’t care why we want a feature; they should just build it.
* They should quit trying to be a product manager, and just do their job.
Never forget that you depend on their cooperation, their buy-in, and their motivation to ship software.
Remembering that, work to create an environment where those things can flourish. An environment that is safe for everyone to present ideas. One that allows them to self-organize, and re-organize, as needed. Where they know the “WHY?” behind every request. Where listening and thinking are as valuable as talking, and questions are as important as telling.
When you build that kind of environment, you’ll happily trust the team with the control they have.
If you don’t, you’ll constantly be trying to get control of things that you can’t.
Do you see how much you depend on your team’s motivation?Do you see people who pretend they don’t?
The secret authority of coders. 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.