Product strategy before anything was built
AMillionPaths did not come to us as a blank brief. There was already a patent specification and an early prototype to build on. Rather than treat that as a finished plan, we started with how people think about their own careers. Through personas and journey mapping we worked out what would make someone want to document their path, and how to guide them through it without it feeling like filling in a form.
But the deeper work was in the questions themselves. In close collaboration with the client, we ran research and development into what the platform should ask a contributor, and how to ask it. The aim was not simply to capture a career, but to draw out the reflection and detail that make a path genuinely useful to others: the insight that future members will value as they explore real journeys and make connections in later releases. Getting those questions right is what turns a documented path into something worth learning from.
From wireframes to a high-fidelity prototype, we tested the core product flows with real users and refined them before any production code was written. Getting the experience right while it is still cheap to change is what protects a startup’s investment.
But the deeper work was in the questions themselves. In close collaboration with the client, we ran research and development into what the platform should ask a contributor, and how to ask it. The aim was not simply to capture a career, but to draw out the reflection and detail that make a path genuinely useful to others: the insight that future members will value as they explore real journeys and make connections in later releases. Getting those questions right is what turns a documented path into something worth learning from.
From wireframes to a high-fidelity prototype, we tested the core product flows with real users and refined them before any production code was written. Getting the experience right while it is still cheap to change is what protects a startup’s investment.