Back to Journal

What to settle before you build.

Start with the people, the work and the decisions that shape a useful product.

Name the problem.

Describe the task that needs to change. Who does it now? What takes too long, gets repeated or causes mistakes? A clear problem gives the team something useful to design around.

Follow the real work.

Walk through one task from start to finish. Include the people, documents and tools involved. Look at what happens when something is missing or a request needs approval. The exceptions often reveal more than the ideal path.

Agree the first release.

Choose the smallest set of features that completes a useful journey. Write down what belongs in the first release and what can wait. This makes design reviews, estimates and testing more focused.

Plan for daily use.

Decide who will manage the system, answer questions and keep information current. Set aside time for training and support. Launch is a milestone; the product still needs care after people start using it.

Have a project in mind?

Talk to Indeginus
A website your team can update.Designing connected event experiences.