Friday is booked.
Monday is only proposed.
A design challenge for Krane. A working internal tool that turns supplier messages, site updates and approvals into one clear next decision.
- Role
- Solo designer and researcher. I wrote the code myself, using AI coding tools
- Timeline
- September 2026
- Context
- Design challenge for Krane
- Study
- Five construction professionals, six tasks each
How these were measured
One unmoderated round with five construction professionals, recruited through UX QuestionPro and paid $70 each. I read their submitted responses rather than watching sessions. No retest yet, so there’s no before and after.
From the team behind Krane.

“Nate did a design challenge for us at Krane, and he didn’t stop at Figma. He built a working app in React, and turned it around fast. Our whole product lives or dies on whether people trust what the AI tells them, and he nailed that right away. Would recommend him to anyone building AI products.”
Every message changes something, and it’s hard to tell what.
Krane asked me to use AI to make sense of construction information while keeping people in charge. A summary that sounds confident can hide the one condition that matters.
- A production date can be mistaken for an arrival date.
- A receiving window can be mistaken for a transport booking.
- A lower price can look better before freight is added.
Make checking easier, without hiding what’s still uncertain.
A review step only where a wrong reading could cost money, time or material. No checkboxes everywhere.
In testing, all five people could tell what was booked from what was only proposed.
Five construction professionals, six tasks each.




One queue for the people who run the job.
Coordinators track dozens of materials across email, a spreadsheet and phone notes. The tool is built around three jobs: find what changed, decide the next step, hand it to the right person.
What’s inside
- Work queueOne owner, one next action and a due time per material.
- Delivery reviewThe AI’s reading next to the original message, before anything changes.
- Supplier comparisonQuotes on the same basis. Freight applies only after review.
- AI quality reviewCorrections tested against current behavior before they go live.
All four share one demo library of status, evidence and review patterns.
- Project coordinatorKeeps every material moving and assigns its next action. Reviews AI readings and drafts requests.
- Procurement leadSets the price basis and applies freight answers. Doesn’t book deliveries.
- Receiving leadConfirms space, crew and access on site.
- Project managerApproves charges and turns on corrected AI rules.
Needs a decisionNorthline and Harbor · 4 items
Sorted by what blocks a date
| Material | What changed | Next action | Owner | Due | Status |
|---|---|---|---|---|---|
| AHU-04Air handling unit | Rev C still under review. Fabrication stays conditional. | Clarify drawing and fabrication conditions | Jamie Davis | Tue 12 PM | Blocks a date |
| CHLR-02Chiller | Carrier reply sounds positive. Four requirements still open. | Confirm access and unloading | Alex Morgan | Wed 3 PM | Needs checking |
| SWGR-01Switchgear, Northline | Earlier $5,000 freight answer found. | Review and apply freight | Priya Shah | Thu 10 AM | Ready to review |
| SWGR-02Switchgear, Harbor | No production slot for October 19. | Ask Apex for separate availability | Priya Shah | Fri 5 PM | Unconfirmed |
Who can do what
| Action | Project coordinator | Procurement lead | Receiving lead | Project manager |
|---|---|---|---|---|
| Review an AI reading | Yes | Yes | Yes | Yes |
| Send a clarification request | Yes | Yes | Yes | Yes |
| Apply a freight answer to a comparison | No | Yes | No | Yes |
| Approve a charge, like Monday’s $450 | No | No | No | Yes |
| Turn on a corrected AI rule | No | No | No | Yes |
Every change leaves a record
- Jamie Davis reviewed the carrier update. Friday stays booked.
- Jamie Davis sent a request to Alex Morgan with 3 sources attached.
- Priya Shah applied Beacon’s $5,000 freight from the September 10 email. Beacon now $99,000 delivered.
A positive reply doesn’t mean it’s decided.
CHLR-02, a chiller for Northline Medical Pavilion. Friday 9 to 11 AM is booked. Monday is proposed at $450 more. Receiving space is supported, and four requirements are still open: route and access, unloading crew and equipment, written charge approval, and revised carrier confirmation.







Comparing two quotes on the same basis.
-
- Situation
- For one switchgear package, Apex was $100,000 delivered and Beacon $94,000 before freight. Ranking those two numbers side by side would be comparing two different things.
- Call
- Keep the price basis visible and show the break-even: $6,000 of freight makes the totals equal. The only next action offered is reviewing Beacon’s earlier freight answer.
- Result
- Instead of a misleading ranking, the missing number turns into a specific question.
-
- Situation
- Beacon had already quoted $5,000 freight. A later confirmation referred back to it and added terms and an offer deadline. The answer was already there. It just wasn’t usable.
- Call
- Show both records beside their interpretation and the arithmetic. A checkbox confirms both apply, then Apply updates the comparison. I kept reviewing and applying separate on purpose.
- Result
- Beacon comes to $99,000 delivered, $1,000 below Apex on that basis. Applying it doesn’t approve a purchase. In testing, 3 of 5 completed this step, which makes it the clearest thing to fix next.
-
- Situation
- Apex’s slot finishes production the week of October 5, and Northline needs the package on site October 12. Beacon’s capacity is unconfirmed, and Harbor needs its own option for October 19.
- Call
- Keep availability as its own check, with a connector that lands clearly on the project the slot supports. Ask for separate availability instead of quietly reallocating a commitment.
- Result
- A cheaper option never looks available, suitable or approved just because it’s cheaper.
Planning for when the AI can’t finish, or gets it wrong.


I ran a real test: 24 model calls scored by an AI judge against a saved rubric. Missed transport handoffs fell from 3 of 10 to none, and rubric failures from 8 of 60 to 4. Four citation errors remain.
Six things I left out, and why.
Checkboxes on every step
A review step sits only where acting on a wrong reading could cost money, time or material. Everywhere else there is no checkbox.
A price ranking
Two quotes on different bases don’t get ranked. The missing freight number becomes a question to answer first.
One-step review and apply
Reviewing never changes a booking or approves a charge. The cost: 3 of 5 finished this step in testing.
A generic success message
After a partial reply, a plain “done” leaves the coordinator guessing. The record says what’s still open.
AI fixes that go live at once
A correction becomes a proposed rule and gets compared against current behavior before anyone turns it on. It applies to future updates only.
A time-saved claim
The study had no baseline, so I don’t claim any time saved. That waits for a pilot against how a customer works today.
Not built yet: queue rows that open the message they came from, and filtering the queue by owner. Both are fast follows that don’t block.
Small fixes that changed what a screen meant.




The prototype, running in code.
I built Krane as a working app in React and TypeScript, with its own AI runtime and automated tests. Here it reviews a carrier email, keeps Friday as the booking and lists the four things still missing.
The bar it has to pass to ship
“Ready to ship,” written as checks that read the demo library’s tokens and run on the work queue in this page.
Has to pass
- Colors come from the libraryPass
- Type uses the library’s sizes, weights and fontPass
- Spacing stays on the 4 to 48 scalePass
- Every status is an approved label with an iconPass
- Every row has an owner, a next action and a due timePass
- Text contrast is at least 4.5:1Pass
- What the AI read never claims certaintyPass
- No em dashes in the copyPass
Fast follow, doesn’t block
- Each row opens the message it came fromOpen: no source links yet
- The queue can be filtered by ownerOpen: not built yet
8 of 8 pass at desktop and 390px wide. The first run found 12 colors, the font and 4 spacing values off the library, so I moved the queue onto the shared values.
Where people still got stuck.
What I’d change
Watch sessions instead of only reading submitted answers. Unmoderated responses told me who got stuck, but not always why.
What I’d do next
Fix the three places people stumbled: drawing requirements, the freight review-and-apply step, and the difference between receiving availability and unloading readiness. Then retest.
What I’d validate
Run a small shadow pilot next to how a customer’s team works today. Main measure: correct next actions. Guardrail: missed conditions. A 20% cut in whole-task time is a target to test, not a result.