The Corky Process is meant to produce long term results through galvanizing resilient systems through continuously adapting to changing circumstances.
“Change is the only constant in life”
Heraclitus
These are generally the flows, however, these steps are more guidelines than hard rules. The first 3 steps are planning and the last 3 steps are execution. The complete loop looks like:
Learn > Define > Design > Build > Measure > Learn
It’s a combination of two methods from Balance, Innovation and Design and The Lean Startup as well as some other things I’ve developed or found, which is I think the essence of the Corky process.
Planning
Learn > Define > Design
Thank you to the TeamTreehouseUX Tech Degree as well as Balance, Innovation and Design:
Learn: dedicated to collecting all relevant information as the foundation of all future work. It’s most important to build a deep understanding of your end-user and context of use.
– User Personas
– Empathy Maps
– Affinity Maps
– Journey Maps
Define: dedicated to making sense of the information collected in the previous stage by framing it into clear and fact-based opportunities, constraints, and experience principles to inform the process of design.
– Road Mapping
– Story Boarding
– User Flows
Design: dedicated to visualizing solutions informed by the previous stages. Visualization can take many forms like written concepts, illustrations, CAD, physical prototypes, and high- and low-fidelity interactive digital prototypes.
– Low Fidelity Wireframes
– High Fidelity Wireframes
– Mock Ups
Execution
Build > Measure > Learn
One method that I find particularly helpful is the build, measure, learn feedback loop from the book The Lean Startup.
Handling Work Package
Github
In the event we’re collaborating on a project, the workflow that I employ when working with Git is defined below. This is how the work is actually done. To get started with Git, you want to follow these steps to enter the flow chart below:
1.) Clone the repo with git clone repoUrl
2.) Checkout a dev/feature branch with git checkout -b newBranchName
3.) Make your changes (add and commit) and push to the remote repo with git push origin newBranchName, not master. Only pull or fetch from master.
4.) Go to the github page and submit a pull request, making sure the base is the master branch.
System Wide Perspective
Below is a value stream map for full development of app ideas, like games, that can be build like a startup. A methodology I like is the Build-Measure-Learn feedback loop from the book “The Lean Startup” by Eric Ries. This means once you reach the end of this page, consider starting back here at the top.
