Matthew Stracke

Why this persona fits the audience

He works with a 7-person delivery pod in a UK healthcare supplier and coordinates work on internal request portals, approval flows, and service dashboards. The team currently uses a competitor low-code platform for part of its app portfolio, while other processes still sit in spreadsheets and email-based handoffs.

• Age: 39
• Location: Birmingham, United Kingdom
• Occupation: Scrum Master
• Income: GBP 71k base salary
• Education: Bachelor's in Business Computing
• Company size: Mid-sized (250-1000 employees)
• Years in role: 4

“It's all about finding that sweet spot where we can deliver value quickly without creating a tangled mess down the line.”

Matthew Stracke, 39, has carved out a niche for himself as a Scrum Master within the UK healthcare supply sector, a role he's held for four years. His journey into IT began with a Bachelor's in Business Computing, a degree that provided him with a solid foundation in both technical concepts and business principles. This blend has proven invaluable in his current position, where he leads a 7-person delivery pod tasked with enhancing internal operational efficiency. His team is currently navigating the complexities of a competitor's low-code platform, using it to build out internal request portals, streamline approval workflows, and develop service dashboards. However, this modern approach coexists with a significant amount of legacy work, where processes are still managed through spreadsheets and manual email exchanges, a situation Matthew is keen to improve. He lives in Birmingham with his wife and two children, a life that grounds him and reinforces his commitment to creating stable, reliable systems. His income of GBP 71k reflects his experience and the critical nature of his role. Matthew is driven by a desire for predictable delivery and a deep-seated belief in collaboration, always seeking to empower his team and serve the end-users of the internal applications. He's pragmatic, preferring to build upon existing strengths rather than advocating for radical, untested overhauls. Recent decisions have focused on incremental improvements to the existing low-code implementation, prioritizing user feedback and demonstrable gains in efficiency, while also exploring options for better integration with the remaining manual processes. He views time as a valuable resource, both for his team's sprints and his own family life, and is constantly looking for ways to optimize workflows without sacrificing quality or team morale. His approach to money is sensible, focusing on long-term stability and value rather than immediate gratification.

Background & daily life

A day in their life

Matthew's day typically begins around 6:30 AM with a quick run or checking urgent emails. After getting his children ready for school, he commutes to the office, often listening to an agile podcast. His workday starts with a daily stand-up with his 7-person delivery pod, followed by tackling impediments, reviewing user stories, and collaborating with developers. He might have a meeting with a stakeholder to clarify requirements for a new internal portal or discuss progress on an approval flow. Lunch is usually a quick sandwich at his desk while catching up on industry news. The afternoon involves more team coordination, perhaps a sprint planning session or a retrospective, and documenting decisions. He aims to leave by 5:30 PM to be home for family dinner.

Lifestyle

Matthew lives in a semi-detached house in a suburb of Birmingham with his wife, Sarah, a primary school teacher, and their two young children. His evenings are typically spent helping with homework, preparing dinner, and catching up on family time. Weekends often involve trips to the park, visiting family, or occasional DIY projects around the house. He tries to fit in a run three times a week, usually early in the morning before work, to manage stress. Financially, they are comfortable but mindful of saving for future goals like home improvements and the children's education. He's not one for extravagant spending, preferring practical purchases and experiences.

Work life

As a Scrum Master for a UK healthcare supplier, Matthew navigates the complexities of supporting a 7-person delivery pod. His primary focus is on coordinating the development of internal request portals, approval flows, and service dashboards. The team juggles a competitor's low-code platform for some applications, but significant processes still rely on outdated spreadsheets and manual email handoffs, creating friction. He spends his days facilitating ceremonies, removing impediments, and ensuring the team adheres to agile principles while pushing for better integrated solutions. The pressure to deliver reliable, user-friendly internal tools is constant, especially given the healthcare context.

Relationships

Matthew is close with his wife, Sarah, who is his primary confidante and support system. He maintains good relationships with his parents and a few close friends from university, with whom he shares common interests in technology and sports. Within his work, he has a strong rapport with his development team and a generally positive, collaborative relationship with the product owner and key business stakeholders, though he sometimes finds it challenging to manage expectations.

How they decide

Matthew is a methodical and research-oriented decision-maker. He values input from his team and relevant stakeholders, often gathering data and weighing pros and cons before committing to a course of action. He's not impulsive and prefers to understand the implications of a decision thoroughly, especially when it involves new tools or significant process changes. Peer consensus and evidence-based reasoning are important to him.

How they sound

Matthew speaks with a clear, moderate cadence, using standard British English. He tends to be articulate and avoids overly technical jargon when speaking with non-technical colleagues, opting for simpler explanations. He's generally positive and encouraging but can become more direct when discussing process blockers or risks. He uses phrases like 'right then,' 'let's get this sorted,' and 'what's the best way forward?' He's careful not to sound dismissive of existing tools or processes, even if they are suboptimal.