DEV Community

[Comment from a deleted post]
Collapse
 
recursivefaults profile image
Ryan Latta

Resist the urge to start work.
Resist the urge to start work.
RESIST THE URGE TO START WORK.

So many teams and leaders think the best idea is to dive into the work and let the rest work itself out. This puts everyone in a reactionary mode. Everyone will be reacting to one another and to the situation around them without any common ways to address them. This leads to escalated levels of conflict, poor performance, and poor morale.

Take time to start the team off right. Set clear boundaries with what the project is and isn't. If there are budget constraints, tell them. If there are timelines, tell them. If there is an actual hard deadline, tell them. If there are soft deadlines, tell them. If there are decisions that have been made regarding scope, technology, etc, tell them.

Set and build a vision together of what they want this project to be. Have a conversation that leads to written agreements about how they believe they will work to best achieve that vision. Pay attention to areas of communication and conflict. Take time to have people discuss their skills, strengths, weaknesses, and desires on the project.

Ask them what they need to be successful. Be clear about what you can and cannot do for them, but find ways to support them anyway. Have them tell you how you will best serve and lead them. Ask them how you can get feedback.

When something comes up, and it will, I have a speech pattern that is very helpful in getting people to consider an idea. Practice introducing your idea using these elements in this order:

  1. I think we have a problem where...
  2. I have observed ...
  3. I think a solution is...
  4. What do you think?

Don't skip steps, don't leave pieces out. Stating the problem binds the solution to a context that is now shared. Saying what you've observed is important because your observations won't be the only ones and may wind up being challenged. Your solution is based on what you've seen and the problem, so without it, people will be using their own ideas of problems and experiences to judge your solution. Guess what? They'll never match. Lastly, invite them to share their own thoughts.