Chapter 03
Workflow thinking
Translate features into closed-loop workflows that change daily site behaviour.
01
What this lesson is about
Most construction technology is sold and bought as features. Search. Playback. Compare. Export. AI detection. Heat maps. Timelines. Each is genuinely useful in the right hands, and each leaves the user holding the bag for turning the output into action. This lesson teaches the alternative frame, which is workflow thinking. A workflow has a trigger, an activity, a decision, an action, and a closeout record. By the end of the lesson you should be able to take any feature your vendor demonstrates and ask the four questions that turn the feature into a workflow proposal. The skill is not abstract. It is the difference between platforms that change site behaviour and platforms that produce another tab nobody opens by week six.
02
Feature thinking and what it leaves behind
A feature gives a user a capability. Searching for a person near a machine is a capability. Comparing two 360 walks side by side is a capability. Exporting a clip with a watermark is a capability. None of these closes a loop on its own. Feature thinking puts the cognitive burden on the user: see something, decide what it means, decide who owns it, decide what evidence is needed for closeout, decide whether it should be escalated, decide whether a similar finding has appeared before. That mental load is the reason platforms with extensive feature lists often fail to change the project rhythm. The feature is bought, the feature is enabled, and the feature is then used by the most diligent member of the team for two months before quietly fading. The fade is not a vendor failure. It is a workflow gap.
03
The trigger-evidence-action loop
A workflow is a closed loop with five named stages. The trigger says when the workflow starts: a person enters a controlled area, a delivery arrives without a docket, a clash is identified, a payment application is submitted. The activity says what the workflow does to the trigger: capture, compare, route, attach, score. The decision says what conclusion the activity reaches and who is the named owner of the conclusion. The action says what the workflow then does in the real world: an observation is created, a hold is placed on the load, a non-conformance is logged, a payment is approved or queried. The closeout record says what the workflow leaves behind so that an external reviewer in three months could reconstruct what happened and why. A workflow is complete only when the closeout record exists. Without it, the loop is not closed and the workflow is, at best, a habit.
04
A worked safety example
Take a typical safety scenario: a person on foot near a moving telehandler. Feature thinking would describe a system that detects the proximity, draws a box on the person, and surfaces an alert in a feed somewhere. Workflow thinking goes further. The trigger is the proximity event itself. The activity is the automated detection plus a human review to suppress false positives. The decision is whether the event becomes a recorded safety observation, with the supervisor on the package as the named owner. The action is the observation routing into the daily safety stand-up, the supervisor speaking to the operator, and the toolbox talk being scheduled if the same event recurs in the same crew within a week. The closeout record is the observation log entry, the toolbox attendance sheet, and the next week’s recurrence count. The same trigger in feature thinking produces an alert; in workflow thinking, it produces a closed loop with a measurable recurrence rate.
05
How to convert any feature into a workflow proposal
When a vendor demonstrates a feature, the discipline is to interrupt the demo with four questions. What is the trigger that makes this feature run on a real site without someone deciding to open the tool. Who is the named owner of the decision the feature points towards, and how do they receive it. What evidence is preserved as the closeout record, and where does it live for six months and beyond. What does the recurrence look like, and how does the command view surface it. If the vendor cannot answer any of the four, the feature is real but the workflow is not. Buy the feature only if the workflow can be designed in-house, and treat the design work as part of the cost. Workflow thinking is the buying habit that distinguishes mature RDI customers from the projects that accumulate tools and continue to run on email and spreadsheets.
Practice
01. Take the most recent feature demo a vendor gave your team. Write down the four workflow questions and answer them honestly. If any are missing, identify who would need to design the gap in-house.
Look for: A strong response surfaces at least one missing element of the closed loop and names a specific role responsible for designing it.
02. Pick one workflow on your current project that runs on email or a chat thread. Sketch the trigger, activity, decision, action, and closeout record on a single page.
Look for: A strong response identifies the missing closeout record as the main reason the workflow is informal and proposes a single owner.
Checkpoint
Pick one construction technology capability and describe the workflow it should complete.
Recommended reading