/PLAYBOOK: 8 PRINCIPLES
HOW WE
RUN PROJECTS.
The working principles behind scoping, delivery, ownership, documentation, and support.
/01
DEFINED SCOPE
Each project begins with written deliverables, assumptions, exclusions, responsibilities, and a change process.
/02
WORKING DEMOS
Regular demos keep feedback tied to the product and surface decisions while changes are still manageable.
/03
DIRECT COLLABORATION
Clients work directly with the person responsible for product decisions and implementation.
/04
CLIENT OWNERSHIP
Code, repositories, infrastructure access, and documentation are transferred to client-controlled accounts.
/05
APPROPRIATE TOOLS
Technology choices follow the product requirements, operating constraints, and the team's ability to maintain the result.
/06
DOCUMENTED HANDOFF
Every launch includes the technical notes and walkthroughs needed to operate and extend the product.
/07
MEASURED RELEASES
The first release focuses on a usable workflow that can generate feedback before the product expands.
/08
POST-LAUNCH OPTIONS
Maintenance and continued development are available, or the product can be handed off for internal management.
/THE PRINCIPLE BEHIND THE PRINCIPLES
Clear project mechanics make it easier to evaluate progress, make decisions, and take ownership of the result.
/PUT THESE TO WORK
BOOK A 30-MIN CALL.
Bring the problem, current workflow, users, and constraints. The first call will focus on the most useful next step.