Choosing what to build and what to adopt

Choosing a platform starts with understanding the work it needs to support. A custom build is not automatically more thoughtful, and an existing product is not automatically a better fit.

Describe the important differences

List the behaviours that are essential to the experience. Separate requirements from preferences and from assumptions that have not yet been tested. An existing product may already support the difficult parts, while a custom interface may still be useful around a distinctive workflow.

Consider everyday ownership

Think beyond the first release. Who will maintain the content, investigate an error and handle a change in requirements? The people operating a system need a practical understanding of it, not just a successful demonstration.

Test the uncertain part

Use a focused prototype to investigate the most consequential uncertainty. Document what it demonstrated and what it did not. A clear decision records the tradeoff and leaves room to revisit it when the requirements change. The best choice is the one that remains understandable in the context of the actual work.