← Back to BuildSample · made-up company
Prototype Walkthrough · Tab & Shift EngineeringFloor 16 Technologies
Build

Prototype Walkthrough: Project Register

Tab & Shift Engineering Ltd. · The first prototype, click by click, and what four sessions changed

Prepared forPrepared byDateStatus
Marcus Chen
Chief Operating Officer
Floor 16 TechnologiesSep 28, 2026v1.0 · Live

Summary

Tab & Shift's project list lived in a 14-tab workbook that three people edited and nobody trusted. In the first session, leadership clicked through a working register built on their own 142 projects. Four sessions later the workbook went read-only.

142live projects loaded from the workbook before the first session
4weekly working sessions, 45 minutes each, over Teams
11 / 3changes made, and features cut, between session 1 and handover
4 minfrom a project's approval to a ready project site

What we started with

Loading the workbook into the register was the first test. It turned up these problems before anyone had clicked anything.

Found in the workbookRowsWhat the register does instead
The same project number used twice9Issues the number itself. Nobody types one
No project manager named23Requires one, chosen from the staff directory
Dates that do not exist, such as September 316Date fields that only accept real dates
Status shown only as a cell color142Stage and Health are columns you can filter
Budget retyped from accounting each month142Reads it nightly from the accounting system

Session 1: the register, on your data

Week one, September 3. In the room: Marcus Chen, Elena Rossi, Daniel Brooks and Priya Shah. Everything shown was live in Tab & Shift's own SharePoint, on the 142 real projects.

  1. 1Mine. Elena sees her 11 projects and nothing else. The default for every project manager.
  2. 2At risk. The 7 projects whose managers marked them at risk, each with the reason they gave.
  3. 3Open P-2231. The project record opens in the same page.
  1. 4Update health. The project manager sets On track, At risk or Off track. A reason is required for anything but On track.
  2. 5Open project site. Straight to the project's SharePoint site and its five libraries.

"Health should be my call, not a formula. A formula would have said this one was fine until it wasn't."Daniel Brooks, session 1

Sessions 2 to 4: shaped by the people who use it

Each week opened with what had changed since the last session, then one new part of the register. Sam Okafor joined from session 2, once project setup was on the table.

  1. 6Client. Typed ahead from a client list. The workbook had 61 spellings of 38 clients.
  2. 7Submit for approval. Goes to the division lead in Teams. No number yet, so abandoned requests never use one up.

What each session showed and decided

SessionShownDecided
1
Sep 3
Register home and project record, on all 142 projectsStage cut from 9 values to 5. Health set by the project manager with a reason, not calculated. One project manager per project, a person rather than typed text.
2
Sep 10
New project form, approval in Teams, site built in four minutesThe number is issued on approval, not on request. Client chosen from a list. Every project site gets a Field library, which went into the folder standard.
3
Sep 17
Budget from accounting, permissions, the old workbook's historyContract value and budget visible to project managers, division leads and Finance only. Budget read nightly and never edited here. 96 closed projects imported as Closed.
4
Sep 24
Leadership view, the Friday update, the role guidesThe workbook goes read-only on September 28. Project managers update health by Friday noon. The leadership view replaces the Monday status email.

What changed between week one and handover

ChangeWhatSession
AddedClient list: 38 clients, cleaned from 61 spellings2
AddedA reason required whenever health is not On track1
AddedBudget used, read nightly from the accounting system3
AddedLeadership view4
AddedA Teams reminder to project managers at 10 AM on Fridays4
Added96 closed projects from the workbook, kept as history3
AddedA Field library on every project site2
ChangedStage values, from 9 to 51
ChangedProject manager, from typed text to a person1
ChangedProject number issued at approval, not at request2
ChangedBudget used shown as a bar against contract value3
CutA Gantt chart per project. Schedules stay in the scheduling tool, linked from the record2
CutA weekly email digest to all staff. Nobody wanted another email3
CutTimesheet hours. They stay in the accounting system3

Why cut anything. Each cut feature had a home already, or nobody would use it. Cutting them kept the register to one job, the list of projects everyone works from, and kept the build inside four weeks.

Where it stands

Sample on a made-up company. Figures are scenario numbers, rounded. Real prototypes are built on the client's own data in their own SharePoint.