Find the real decision
Look beneath the technology question. Name the outcome, the person responsible, the evidence needed, and what would make the work wrong.
The actual screen recording
Watch Ryan turn the need into an assignment.
Ryan begins with the exact prompt he gave the project agent—a language model connected to approved project files and tools, working within written rules and human review. The recording then follows the evidence handling, editable proof artifact, defect repair, and final check in order.
Hover: instant preview · Click: full film + score · 2:24
The SDA consulting method
SDA defines what the work must prove.
Ryan sets the objective, limits the evidence to approved sources, and names the proof required before delivery. The project agent works inside that structure, while consequential interpretations and decisions remain with people.
Build the working structure
Connect the approved sources to persistent project state, explicit approvals, and handoffs that can survive across sessions.
Direct the work
Choose the right tools, write a clear assignment, and keep each output connected to the objective and current project state.
Inspect before delivery
Test the work, challenge weak interpretations, repair defects, and leave the decision and next action clear.
The rebuilt applied artifact
SDA built the workspace the request required.
The workspace keeps the reasoning connected from the original objective through the next action. A reader can open all seven fictional records to inspect the evidence, decisions, and ownership. They contain no student data and do not provide legal, medical, educational, eligibility, or accommodation advice.
4 source-linked records1 counterexample retained2 human approvals open5 owned next actions
The decision this cycle supports
Which program supports appear promising enough to continue, what remains uncertain, and what should be observed next?
Every factual statement resolves to a source; uncertainty is explicit; consequential decisions remain human-owned.
The visual sequence may help participants anticipate the next activity.
The visual sequence is a plausible, low-burden support worth observing further. The current records do not establish that it caused the faster transition.
Supports E-002 + E-004
Complicates E-003 and 3 open gaps
Decide what to continue observing before discussing any program-support change.
Continue the visual sequence for three comparable sessions while collecting the same transition measure and one accessible feedback item?
GuardrailPresent the visual sequence as a support under observation, not a proven intervention.
Next stateApprove, revise, or reject the three-session observation plan.Owner: Program professional · Status: OPEN
Open the working system →
Inspectable by design: a reader can trace each observation to its source, see counterevidence beside the preferred interpretation, and tell which decisions still require a person. The next cycle already has an owner.
The consulting skill behind the demonstration
Ryan found the real assignment before writing the prompt.
The original request sounded like a question about prompting. Ryan asked for scope and detail, heard the need for continuity, and chose a project workspace where evidence, decisions, and next actions could persist. Then he turned that judgment into the exact assignment shown in the film.
Find the job beneath the technology question.
“I need a partner that can build these projects with me … a bridge between idea and completed project.”
Ryan’s first move was to ask about scope and the right level of detail. That clarification exposed the real job: keep the objective in view, retrieve context, produce the next useful component, challenge the reasoning, document decisions, and recommend what happens next.
“Stop engineering prompts. Start writing loops.”
The insight was not merely to write a longer instruction. It was to design a repeatable cycle in which context, decisions, files, review, and next actions survive each answer.
The division of labor: conversation draws out intent, nuance, and human judgment. The workspace carries the approved evidence, files, review, and next actions.
The prompt defined the evidence, objective, deliverable, audience, and quality bar.
- Move the selected screenshots out of Downloads and into the project.
- Rename and organize the source material to a consistent standard.
- Analyze the full conversation and recover the person’s actual objective.
- Make the reasoning visible because the complete build is being recorded.
- Create one polished, editable artifact that demonstrates the idea.
- Think the work through, coordinate the steps, and meet SDA’s quality standard instead of waiting for every click to be prescribed.
“Actually, I’ll do you one better to demonstrate this.”
Ryan opened the workspace and recorded the complete working cycle. The project agent organized the evidence, created an editable proof artifact, repaired the defects found in review, and left the project ready to continue.
- Interpret before actingState the person’s real objective before touching the files.
- Make source handling visibleShow what was preserved, organized, removed as repetition, and used.
- Produce inspectable workCreate a real project artifact a person can open, challenge, revise, and continue.
- Review before declaring successFind the layout and privacy problems, repair them, and check again.
Conversation→System design→Directed execution→Checked decision
Navigating ambiguity. Ryan finds the decision beneath the original question, designs a controlled way to do the work, and leaves the result ready to inspect and continue.
The consulting moves inside the film
Follow the decisions behind the build.
The timestamps trace Ryan’s reframe, the assignment it produced, the review standard, and the work that remains usable after the session.
- Reframe the questionAsked for one better prompt, Ryan changes the premise: stop engineering isolated prompts and start designing repeatable working loops.
- Identify what the person really needsThe clarification reveals the true job: a partner that remembers context, challenges reasoning, records decisions, and helps bridge an idea to a completed project.
- Give conversation and execution different jobsConversation draws out intent and nuance. The desktop project workspace connects the project agent to approved files and tools so usable state remains behind.
- Turn the advice into a live testRyan promises a demonstration, then gives the project agent the exact recorded assignment instead of describing the concept in the abstract.
- Direct the outcome without scripting every moveThe brief defines the source material, real objective, inspectable artifact, visible reasoning, and quality standard—then gives the project agent room to coordinate the steps.
- Make the first proof artifact earn acceptanceThe recording-era presentation is built, opened, challenged, repaired, and checked for a hidden privacy problem. It proves the review loop; the working system above is the applied consulting outcome.
- Leave durable project stateThe organized sources, written analysis, proof artifact, decisions, and project folders remain available for the next action. The applied system above carries that state into evidence, decisions, and owned follow-up.
The SDA quality standard
Good work survives inspection.
SDA tests whether the evidence, interpretation, approval state, and next action still agree. During the recorded build, review caught both layout defects and a private source image hidden inside an apparently clean file; both were repaired before delivery. Consequential decisions remain with people.
4 evidence records each with a stable source ID1 challenged interpretation support and counterevidence together3 decision records approval state made explicit5 next actions owner, dependency, and status preserved6 quality gates sources, reasoning, privacy, and continuity0 student records public demonstration remains illustrative
Accessible visual proof
Read what happened on screen.
The film has no spoken narration. Authored captions explain Ryan’s assignment, the work performed, and the review that followed. The visual description documents what remains available after the session.
Open transcript and visual-description outline
00:00–00:30: The real request and why SDA moves the work from chat into an organized project.
00:30–01:03: The assignment, the plan, and the source files being organized.
01:03–01:53: The real need is identified; the first proof artifact is built, reviewed, repaired, and checked for privacy.
01:53–02:24: The project folders show what remains after the chat ends and can become the next working cycle.
Applied intelligence consulting
Bring SDA the problem before it has a clean brief.
SDA turns complex problems into clear decisions and working systems. The result keeps the evidence, human decision points, and next action ready for your team to use.