For teams growing faster than their processes
Clear work and healthy disagreement, especially for multicultural and remote teams.
Sounds familiar?
- Work is scattered across tools and spreadsheets
- Too much work, too little time, and everything is top priority
- Arguments turn personal, or people go quiet
- Eight nationalities, eight ideas of what “urgent” means
People and process
Team culture
Coaching and facilitation
Team coaching sessions and facilitated workshops on trust, how you disagree and how you work across cultures.
Arguments turn personal or silent
What I do: agreed rules for disagreeing, practised in team sessions.
Result: people push back openly and still trust each other.
Leadership uncertainty
What I do: keep the team focused, priorities clear and communication honest.
Result: the team keeps delivering, even when the direction is unclear.
Cultural clashes
What I do: make hidden differences visible, like feedback styles and hierarchy, then agree shared norms.
Result: fewer misunderstandings, real belonging.
Ways of working
Processes and tools
I know what agile frameworks are meant to do, and I shape the process and tools around your people, so Jira and Confluence make their work easier instead of becoming one more thing to manage.
Scattered information
What I do: migrate everything into one structured system, from Asana, TFS or spreadsheets.
Result: one place to look, no more lost work.
Everything is urgent
What I do: one visible list of all the work, priorities agreed with leadership, and a limit on how much is in progress at once.
Result: less firefighting, the important things get finished, and the team can breathe.
Healthy disagreement, no toxicity
In every team I’ve worked in, people argue openly about the work, and nobody gets pushed or bullied. That’s the culture I help teams build: one where you can disagree and still trust each other.
Stories from real teams
Team culture
Deciding not to decide
Challenge: a development team split over a technical decision. Both options made sense, and opinions were strong.
What I did: helped the team map what could go wrong with each option and what we’d need to know to choose well. We documented the reasoning and agreed to decide once that clarity arrives.
Result: the team moved forward on everything else, and nobody lost face.
Steady through a founders’ conflict
Challenge: at an identity management startup, the founders came into conflict right after funding.
What I did: kept the team focused and the delivery running while the founders worked through their conflict.
Result: the team kept shipping through the storm.
Ways of working
From scattered sources to one system
Challenge: information came from different places. Every person had their own source and organised their work their own way.
What I did: migrated everything into one structured system and shaped it around each person’s needs.
Result: everyone sees their own tasks, what’s coming up and what others are working on. Management checks the status themselves instead of asking every day.
From constant urgency to clear priorities
Challenge: hundreds of open tickets and priorities that changed too often. The team kept starting new work without knowing what to drop.
What I did: organised the tickets into a clear overview that shows what to prioritise and, more importantly, what to deprioritise, and what risk that carries.
Result: when a new priority comes in, everyone knows what’s paused and why.
Client names withheld.
Alongside these, I can also help with:
Workshops and offsites
Facilitated sessions for alignment, retrospectives and team offsites.
Software quality
Years as a lead test engineer and Head of Quality, so the risk of shipping something broken stays in view.
Coaching for you, too
Leading the team through this yourself? One-to-one coaching for leaders →
Fewer conflicts · clearer work · smoother collaboration across borders
A free 20-minute conversation. No pitch: we look at what’s unclear in your team and whether I can help.