About the practice
Designing the systems people depend on takes more than a strong interface or a clean line of code. It takes a shared view of the whole service.
How we work
Verdant Axis Studio is an independent practice built around multidisciplinary collaboration rather than hierarchy. We assemble teams by problem type and delivery needs, not job title prestige. The right people work directly with the people closest to the service, and decisions stay visible from discovery through delivery.
The people behind the practice
Product Strategy Director
Eleanor brings leadership teams together around the decisions that matter most. She has spent fifteen years shaping product direction in regulated and service-led organisations, and is known for turning competing priorities into a clear, testable plan.
Service Design Lead
Marcus maps the realities behind a service: its workarounds, obligations, and moments of care. He works closely with frontline teams to make service blueprints useful in day-to-day decisions, not just a snapshot for a presentation.
Research & Insight Partner
Priya combines qualitative research with careful analysis of operational evidence. Her work helps teams hear what customers are saying, notice whose needs are missing, and make confident choices without mistaking a loud anecdote for a pattern.
Product Design Lead
Helena gives complex tools a calm, understandable shape. She prototypes early with users and delivery teams, balancing a careful visual point of view with the practical details that make a product work on a busy Tuesday.
Design Systems Architect
Daniel builds design systems that help teams move consistently without forcing every problem into one pattern. He is attentive to accessibility, documentation, and governance, and makes close collaboration between designers and engineers feel ordinary.
Content Design Specialist
Sophie makes product language do useful work: setting expectations, explaining decisions, and helping people recover when something goes wrong. She has designed content for multilingual services and treats clear language as part of the interface.
Software Engineering Lead
Isaac leads engineering with a focus on maintainability and small, observable steps. He enjoys untangling business rules that have accumulated in spreadsheets and translating them into software teams can understand and safely change.
Solutions Architect
Mei connects product intent to a sound technical shape. She is especially thoughtful about integration boundaries, data ownership, and migration paths, helping organisations make architectural choices that account for the systems they already depend on.
Quality Engineering Specialist
Callum helps teams catch the failure modes that matter before customers do. He combines practical test automation with thoughtful exploratory testing, bringing reliability into planning rather than treating quality as a final gate.
Delivery Operations Manager
Aisha makes multidisciplinary work easier to coordinate and easier to see. She keeps decisions, dependencies, and team capacity in view, while protecting enough space for careful craft and honest conversations about what can be delivered.
What guides us
Show the process, constraints, and decisions so people can take part with confidence.
Design for the service that exists, including its obligations, edge cases, and people.
Share context and working practices; do not make progress depend on our presence.
Prefer understandable foundations that can adapt as policy, people, and priorities shift.
Work with the practice