Let real operations shape the next phase

The first version of a digital workflow is not only a deliverable. It is also a way to learn how the business really works.

Once customers and staff use it, assumptions become observable. The business can see what information arrives, what needs clarification, where work waits and which exceptions repeat. That evidence should shape the next phase.

Start with an operating slice

An operating slice is the smallest connected part of the journey that creates value and can be used in real work.

For a print shop, it might be:

Service information on the website
Customer submits job details and artwork
Staff receives the enquiry
Staff quotes and follows up through the current channel

This does not complete the future digital operation. It creates a reliable entrance and a real stream of work that can be studied.

Record friction, not only feature requests

When people begin using the workflow, collect specific observations:

• Which required information is still missing?
• Which questions do staff ask after every submission?
• Which files are unusable, and why?
• Where does an enquiry wait without an owner?
• Which status does the customer repeatedly ask about?
• Which exception forces staff back into chat or a spreadsheet?
• Which manual step is repeated often enough to create delay or error?

“We need a dashboard” is a proposed solution. “Three staff members cannot tell who is following up with each enquiry” is evidence. The second statement is a better foundation for design.

Look for repeated patterns

One unusual request should not automatically become a system feature. A useful rule usually appears when the same problem repeats across customers, staff members or branches.

Suppose customers frequently submit print files with missing dimensions. The next improvement may be better form validation and clearer instructions, not a complete order platform.

Suppose staff repeatedly lose track of which quotations are waiting for approval. A small internal status view may now have a clear purpose, known users and measurable value.

The evidence determines the size of the next step.

Turn observations into system rules

Before building the next phase, rewrite each repeated problem as a rule the business can review.

Observation	Possible rule to confirm
Staff cannot tell who owns an enquiry	Every enquiry has one assigned owner
Customers send a new file after approval	Replacing an approved file requires a new review state
Production starts before payment is confirmed	A job cannot enter production until an authorized confirmation is recorded
Customers repeatedly ask for delivery status	Staff records dispatch information at one agreed handoff

The system should implement confirmed rules, not invent policy through interface design.

Include staff experience in the evidence

Usage data alone does not explain why people work around a system. Staff may be missing information, protecting a necessary exception or avoiding a step that creates duplicate work.

Short, regular review conversations are useful:

• What took longer than before?
• What became easier?
• Which step feels unnecessary?
• What do you still track somewhere else?
• Which customer situation does the current workflow not support?

This is not a request to implement every preference. It helps distinguish training needs from missing business logic.

Decide the next phase by responsibility

A next phase is ready when the business can explain:

• the repeated problem it solves;
• the people who will use it;
• the data it must own;
• the decisions it will enforce;
• the exceptions that remain manual;
• the result that will show whether it helped.

If those answers are unclear, continue improving the current slice or collecting evidence. More features will not make the decision clearer.

Repeat the loop

Digitalization is an operating cycle:

Build a useful slice
Run it in real work
Observe friction and exceptions
Confirm repeated rules
Improve or expand the system
Measure the result

Each cycle leaves the business with better data, clearer language and staff who understand the workflow more deeply. That is how a small first website can become the foundation of a system that genuinely fits the operation.

---

This article describes a general method for improving business systems. It applies whether or not you build with AlphaBlue.