
The Power of Process: How We Work Together
In software development, we talk a lot about building the right thing. But before we can build something great, we have to figure out how we’re going to work together. Enter one of DX-ROI’s favorite parts of the team forming process, the “Ways of Working” session.
Ways of Working should be established before the first line of code is written. A good Ways of Working session isn’t about creating a rulebook or adding process for the sake of process. It’s about agreeing on how we want to work together so we can spend more time solving problems and less time navigating them. It’s about getting the team in the same room, having the conversations that matter, and agreeing on how we’re going to show up for each other.
It’s a time for everyone’s voice to be heard, and for the team to agree on how we communicate, how decisions get made, how we escalate concerns, how we give feedback, and how we track work. It’s an opportunity to create a shared team vision by answering questions like:
- What time zones are we in, and what are the best times for collaboration?
- What are our roles, responsibilities, and areas of ownership?
- What ceremonies or regular touch points do we need?
- How do we communicate? What belongs in Teams, email, or a meeting?
- How do we make decisions?
- What’s the most effective way to surface risks before they become issues?
- How is work organized and tracked?
- What is our Definition of Ready and Definition of Done?
A concern shared early can become a conversation. A difference of opinion can become a better idea. And a disagreement handled with respect can build trust instead of breaking it down. Ways of Working creates space for people to say, “I see it differently.” And that’s a good thing! The goal isn’t to make everyone think the same way. The goal is to make sure everyone feels comfortable sharing their perspective, listening to others, and finding a path forward together.
Once established, don’t forget to revisit and update Ways of Working on a regular cadence. Sprint retrospectives are often a place where team agreements that aren’t working out can be surfaced and course corrected.
When a team has clear agreements, open communication, and the trust to speak up, we spend more time moving forward together.
So, get aligned. Speak up. Listen to each other. And then build something great together! That’s the power of process.
