Sprinting

A sprint brings your team together for 4–6 weeks to explore the problem, test practical solutions, and make clear decisions quickly. It’s structured, hands-on, and designed to cut complexity and create momentum.

Blurred photo of a wall covered with multicolored sticky notes arranged in rows and columns, likely used for organizing ideas or tasks.
People sitting around round tables in a conference room during a meeting or gathering, with large windows showing the outside view.

Ready to actually get stuff done?

Get in touch…

A sprint isn’t about rushing, its about moving quickly. It’s about removing friction, clarifying purpose, and creating the momentum needed for a group to make meaningful progress. Over a concentrated period, normally 4–6 weeks I work alongside internal teams to test ideas, simplify processes, and build the confidence to make decisions.

Sprints are for when organisations feel stuck, overwhelmed by complexity, or weighed down by long, unwieldy processes. They help groups move from discussion to action, while still holding space for reflection, learning, and the realities of power and partnership. 

What does this look like?

A woman with dark hair tied in a bun, wearing a black shirt and dark pants, standing in a room with a large brown paper-covered whiteboard behind her. She is smiling and holding a colorful object. On a table in front of her is a black case open with various markers and supplies, and a laptop. The room has a white wall, sunlight, and various papers and supplies around.

  • Rather than sitting outside the team, I work inside it. I become part of the weekly rhythm—facilitating sessions, supporting workstreams, testing prototypes, and helping the group learn by doing.

  • Each sprint has a backbone of weekly focus areas, but the route through them is responsive. We adjust as new insights emerge. This balance of structure and flexibility helps teams stay aligned while still being able to move quickly.

  • Sprints aren’t theoretical. We create tangible outputs—such as redesigned workflows, draft tools, or decision-making frameworks—and test them immediately with staff or partners.

  • I bring together people who don’t usually collaborate day to day—operations, legal, finance, learning, programmes—to shorten decision loops, reduce handoffs, and make sense of the whole system rather than isolated parts.

  • We document insights, dead ends, and process shifts as they happen. This builds organisational knowledge and deepens understanding of why change is needed, not just what the change is.