Course 2.4 · Curriculum 2026.1
Building an operational surface, not another dashboard
Build the screen a team runs their day from. The kanban board pattern proven across task, work order, purchase order, dispatch and production.
- Estimated effort
- 6 hr
- Lessons
- 47
- Modules
- 8
- Material
- 6 hr
Estimated effort is the sum of the lesson and lab times in the course outline, for this version of the course.
This course is planned and not on sale. The curriculum below is the plan, and it may change before the course opens.
See the courses on sale01What you will learn
7 capabilities, stated as things you can do
Each one is what you should be able to do at the end, not what the course covers. If an outcome is not testable, it is not an outcome.
- Design a screen around a decision a person makes, rather than around the data available.
- Build a board that reads and writes records, with drag-to-transition and an audit trail.
- Handle optimistic updates and the failure that has to roll one back.
- Add a Gantt view over the same records without duplicating the data layer.
- Keep a board responsive with several hundred records on screen.
- Reuse one board family across five different objects using configuration rather than copies.
- Verify the surface as the real user, on desktop and on a phone.
02Curriculum
8 modules, 47 lessons
Every lesson shows its length and its type, from the course outline.
8 modules · 47 lessons · 6 hr of material
A dashboard reports the past. An operational surface is where the work happens. The difference is whether the user can act without leaving it.
- VideoThe one-line test, applied to a buildDoes this tell someone what to do in their job today, and can they do it here? If the answer to either half is no, keep designing.Preview9 min
- VideoReading an operation before modelling it8 min
- VideoThe board pattern, and the seven objects it has carried8 min
- VideoIf it only shows facts, it is wrong: a walk through a failed first draft6 min
- ReadingReading: the seven design gates, stated up front4 min
- LabLab: apply the one-line test to a screen you already built14 min
- LabLab: name the decision a screen exists to support4 min
Columns, cards and transitions as configuration, before a line of write logic exists.
- VideoColumn definition as configuration, not code8 min
- VideoA card as a small, deliberate subset of the record6 min
- VideoModelling a status set that a board can actually render6 min
- VideoReusing a status set across objects without copying it4 min
- ReadingReading: five objects, one board shape, compared5 min
- LabLab: define columns for a new object against the shared component13 min
Drag to transition is a write, not an animation. The validation behind it is most of the module.
- VideoDrag to transition, and the server-side validation behind it8 min
- VideoOptimistic updates, and rolling one back honestly7 min
- VideoAn audit trail on every transition, not just the current state6 min
- VideoRejecting an illegal transition without a silent no-op6 min
- VideoTesting a transition end to end with a real user4 min
- LabLab: build a two-column board with a real transition17 min
Saved views and export are where a board leaves the platform, and where a real defect shipped four times over.
- VideoFiltering, sorting and saved views7 min
- VideoThe CSV export that wrote a formula and the four other components that had it tooUnescaped formula-leading text is a spreadsheet formula injection. The same pattern was found still live in four other production components.9 min
- VideoEscaping export text so a cell never becomes a formula6 min
- ReadingReading: sanitising leading characters before an export4 min
- LabLab: sweep a codebase for the same export pattern14 min
Several hundred cards on screen, and the rendering decisions that keep the board usable at that count.
- VideoPerformance with 400 cards on screen8 min
- VideoVirtualising a long column without losing drag behaviour6 min
- VideoPaginating a board without breaking the one-screen mental model6 min
- VideoDebouncing writes so a fast drag does not fire fifty updates4 min
- LabLab: load-test a board at ten times its design volume14 min
A second view over the same data layer, then Excel-style in-cell typing replacing a crew-staffing spreadsheet.
- VideoA Gantt view over the same data layer, not a second data model8 min
- VideoThe docket scheduler: replacing a crew-staffing spreadsheetExcel-style in-cell typing on a real grid, because that was the only interface people would adopt.8 min
- VideoIn-cell typing on a grid, and the save that has to feel instant7 min
- VideoA keyboard alternative to drag, so the board stays accessible4 min
- LabLab: add a Gantt view to the board you already built15 min
A home screen built from the same components, and the configuration that turns one board into five.
- VideoA My Day home screen: what one person needs to see this morning8 min
- VideoReusing one board family across task, work order, purchase order and dispatch7 min
- VideoConfiguration versus a fork: keeping five boards as one component6 min
- VideoThe board that almost became five different components4 min
- ReadingReading: what changed and what stayed fixed, board to board5 min
- LabLab: add a second object to the same board family15 min
The board a dispatcher uses in a vehicle, and the pass that proves it, on desktop and on a phone, as the real user.
- VideoMobile: the board a dispatcher uses in a vehicle7 min
- VideoVerifying a surface as the real user, not as an admin6 min
- ReadingReading: a verification script for an operational surface5 min
- ReadingReading: the six named end users behind this course’s verifications4 min
- VideoThe dispatcher who could not see tomorrow, and the fix3 min
- LabLab: verify the board on a phone as a field user14 min
- QuizCheck: operational surfaces13 min
04Before you start
What you need first
Assumed knowledge and setup
- Course 2.3. This course builds a substantial component from lesson one.
- Course 2.2 for the server-side writes.
- A Developer Edition org with several hundred test records. The seed script is provided.
Before this course
05Who teaches it
Elliot Saha
Co-founder, Chief Technology Officer
Platform architecture, custom Apex and Lightning Web Components, AI systems, and the Academy platform itself.
06Reviews
No learner reviews yet
This course has not been taken by enough people to publish an honest rating, and we will not print invented quotes on a page that sells verification discipline. Here is what we can evidence instead.
- Assessment
- Lesson checks onlyThis course carries lesson checks and issues no certificate.
- Curriculum version
- 2026.1You enrol into a version. Content changes do not move you mid-course, and your required-lesson count is snapshotted at enrollment.
- Refunds
- 14 daysAn individual purchase can be refunded within 14 days if you have completed less than 20% of the lessons. Team seats are refundable before they are assigned. From the Academy terms.
Start 2.4
This course is in development and not yet open for enrolment. The courses open now are listed in the catalogue.
- 6 hr estimated effort, labs included
- A ShareCo certificate is not a Salesforce certification