A remote process built around visible decisions

1. Understand the current situation

2. Choose the smallest credible solution

The answer may be configuration, repair, integration, automation, a focused custom tool, or a larger build. The reason for the recommendation is documented.

3. Build in reviewable releases

Work is divided into pieces that can be demonstrated and tested. Each release has acceptance criteria, known dependencies, and a recovery path.

4. Test realistic behavior

Testing includes successful use, permissions, errors, duplicates, interruptions, vendor failures, accessibility, performance, security expectations, and recovery where relevant.

5. Verify production

A staging demonstration is not the same as a live release. Production verification confirms the deployed version, critical paths, monitoring, analytics, and known limitations.

6. Transfer ownership

Handoff can include source code, repositories, deployment instructions, environments, vendor ownership, documentation, credential procedures, known issues, and support terms.

Meetings are used for discovery, decisions, demonstrations, and urgent blockers. Written records preserve context between meetings.