Phase 1 with COO Chris Neary

What to clarify in the first phase of a software project

This archived company video features Chris Neary, introduced as Code and Trust COO when it was recorded, on the topic of Phase 1. The companion guide below focuses on decisions that can help a project begin with a shared understanding of the work.

The following is an editorial companion to the archived video, not a transcript.

Make the unknowns visible

Before committing to a feature list, describe the user problem and the result you want to achieve. Then separate what you know from what still needs investigation. A prototype, a review of an existing system, or a conversation with users can each answer a different kind of question.

• Map the current workflow and identify the first user task the product should improve.
• List assumptions about data, integrations, permissions, and user behavior that need to be checked.
• Agree on the outputs of the initial phase and the decision those outputs should support.

An initial phase is most useful when it leads to a clear next step. That might mean refining scope, testing a risky integration, or deciding which features can wait. Agree on the phase’s deliverables and the decision they should support before work begins.

Contact Code and Trust to discuss your project.