SpokGo: Creating shared direction through discovery.

What began as a request for something resembling a familiar messaging application became a broader effort to understand clinical communication and help multiple teams see the problem in a more useful way.

00 / Context

To write The original request, why the problem definition was ambiguous, and what was at stake in a greenfield product.

01 / People

To write What research showed about clinical communication in context.

Evidence to addResearch synthesis

Caption to write What the synthesis made visible that the original request did not.

02 / System

To write How communication actually moved through clinical workflows, and the system models used to explain it.

Evidence to addCommunication and workflow mapping, system models

Caption to write How this map helped multiple teams see the same problem.

03 / Gaps

To write Where what people were trying to do and how the system worked didn’t line up, and which of those gaps were worth solving.

04 / Design

To write The early product framing, how stakeholders aligned on it, and the role leadership played in making shared direction visible.

Evidence to addConcepts, prototypes, and the artifacts that helped the team align

Caption to write Which artifact moved the conversation, and how.

05 / Impact

The important outcome is not simply that an interface was designed. It is that the organization gained a clearer understanding of what it was building and why.

To write Concrete evidence of that shift, and representative SpokGo product work.