Skip to main content
About

A practice built around the work.

Creative Athletes is a small, senior practice in strategy, design, and engineering. We are organized around the work, not around growth for its own sake.

Practice

The shape of the work.

We are a small group of strategists, designers, and engineers who advise on, design, and ship the systems modern organizations depend on. The practice exists to help leaders make and operate the decisions that shape the next phase of the work.

Operating model

Senior, small, accountable.

Every engagement is led by the people accountable for the outcome. There is no chain of delivery between the leaders we work with and the people doing the work.

We stay small on purpose. A narrow client list lets us hold the standard we want to hold across strategy, design, and execution. It also means we say no often, and we say it early.

The model favors compounded judgment over scale. The same people who frame the strategy ship the first version of the system that puts it into practice.

Behind the practice

Operators first.

The practice is led by people who have spent careers inside real organizations, doing the work before advising others on it: strategy at consulting firms and inside operating businesses, product and engineering at scale, design for platforms used by millions, and modernization programs in regulated environments.

The experience spans enterprise, startup, and public-sector contexts. It includes the parts of the work that do not show up on a credentials page: the negotiation, the procurement cycle, the legacy system that cannot be shut off yet, the operator who will inherit the new capability.

The perspective behind Creative Athletes is shaped by being on the operator side of those decisions, not only the advisor side. We have shipped the systems we recommend, lived with the consequences, and made the next set of decisions with the benefit of the last.

That posture is what the practice carries forward. We are senior because we have done the work. We stay small because that is what lets the seniority show up in the room.

Disciplines
Strategy · Product · Design · Engineering · Research
Contexts
Enterprise · Startup · Public sector
Industries
Financial services · Telecommunications · Healthcare · Consumer products · Media · Government
Working modes
Advisory · Embedded delivery · Modernization arcs · Board and procurement support
Disciplines

Strategy, design, and engineering as one team.

The disciplines are practiced together because real systems are made together. Each one shapes the others. None of them work well on their own.

01

Strategy

The position of the business, the choices that follow, and the operating model that turns those choices into work people can run. Strategy that ignores execution does not survive contact with the organization.

02

Design

Product design that shapes how the work feels, how the system is understood, and how it earns trust over time. Design is the discipline that holds the user inside every other decision.

03

Engineering

Architecture and engineering that put the strategy into production and keep it running. We build systems people inherit. That ownership horizon shapes every technical choice.

Fit

The work we are built for.

We work with founders building the first version of something, leadership teams reshaping the operating model of an existing business, and public-sector organizations modernizing services people depend on.

The common thread is consequence. The decisions matter to the organization. The system that follows the decision will be used by real people for years.

We are less well suited to staffing gaps, brand-led work without operational depth, or programs that need a hundred people to start. We will tell you that early.

Engagements

Scoped to the decision in front of you.

Engagements begin with a short, honest conversation about what you are trying to do and what is in the way. If there is a fit, we propose the smallest engagement that can answer the next real question.

Most engagements run in focused phases: a defined window of work, a clear deliverable, and an explicit decision point at the end. We prefer to earn the next phase rather than presume it.

Accountability follows the same people from the first call to the handover. The team that scopes the work is the team that does it.

Posture

Technology as infrastructure, not trend.

The systems we help build are infrastructure for the organizations that run them. They have to work in real environments, against real constraints, for the people who carry the work forward after we are gone.

We hold the line against features that look impressive in a demo and quietly fail in production. We prefer choices that are still defensible in two years over choices that score well in a quarter.

The bar is durability. The reward, when we get it right, is a system the team that inherits it can defend, extend, and trust.

Get in touch

Tell us about the work.

We respond to every inquiry within a working day. If there is a fit, we will say so. If there is not, we will say that too.