Premise & Practice · Build Days
Jacksonville Founding Build Day
Don't learn AI. Rebuild Your Work Around It.
Learn the Premise to Practice Method by applying it to one recurring part of your job. Name the outcome, question the inherited steps, and leave with a tested AI work system and evidence from real use.
The Jacksonville Beach venue is being finalized. No payment until the venue, schedule, workflow, and fit are confirmed.
Most people point new tools at old work.
You may already have ChatGPT, Claude, Copilot, and a few other tabs open. It is easy to make the current report, deck, or handoff a little faster.
The harder work starts one step earlier: naming what the work is for, challenging the assumptions and artifacts you inherited, and deciding what AI should do, what should stay human, and what happens when the first version fails.
A faster artifact can be useful, but it is not the only possibility. Build Days gives you a disciplined way to question the work, choose a better path, build it, test it, and operate it after the workshop ends.
The work should change for a reason you can explain and prove.
What could you rebuild?
The best project is not the flashiest one. It is the recurring workflow you will use again next week.
Prepare a decision
Turn scattered inputs into a structured brief with sources, uncertainty, and a clear human decision.
Improve project intake
Clarify requests, flag missing information, and reduce the back-and-forth before work begins.
Rebuild recurring reporting
Assemble inputs, draft the narrative, and surface exceptions that deserve human review.
Make feedback usable
Organize customer or employee feedback into evidence-linked themes and an action queue.
Track a moving market
Monitor a defined signal, synthesize what changed, and surface only what deserves attention.
Your Work
A private workbench, document pipeline, tracker, research system, or mini-app.
The form follows the workflow. You are not required to build a public app.
Premise to Practice Method
You are learning how to see inherited work differently, redesign it around current capabilities, and make the result prove itself.
See the work
Map how the work operates now, name what it is for, and surface assumptions that may no longer hold.
Redesign the path
Consider a deliberate improvement and a different way to reach the outcome before choosing what to build.
Define the system
Choose the human and AI split, then define the inputs, boundaries, quality bar, exceptions, and approval points.
Build and break it
Create the smallest useful end-to-end system and test normal work, variation, edges, and failure.
Prove and operate it
Run the system in real work, collect evidence, and decide whether to expand, revise, maintain, rescue, or stop.
Use the method again. The tools can change. The questions, test discipline, and evidence travel with you.
One Build Day, with enough structure to make it stick.
The work is scoped before the room, tested during the day, and used afterward.
75 minutes, virtual
Name the outcome, question the inherited path, choose one useful redesign, and cut it to a buildable scope.
- Complete the prework
- Confirm safe example data
- Leave with an approved Rebuild Hypothesis and build brief
Full day, in person
Apply the method, build the chosen path, test the edges, and document one bounded AI work system with direct support.
- Build your workflow, not a canned exercise
- Run five representative tests
- Set data and approval guardrails
- Prepare a 7 to 10 day field test
1 hour, virtual
Return with real usage. Review what worked and broke, repair weak points, and decide the next move.
- Review field-test results
- Resolve failures and friction
- Lock the operating plan
1 hour, virtual
About 30 days after Build Day, measure persistence, share what changed, and choose whether to expand, revise, maintain, or stop.
- Review the Impact Card
- Identify the next improvement
- Decide what should happen next
A 7 to 10 day field test sits between Build Day and the proof review.
What you leave with
Workflow Definition
The before-state, intended outcome, and inherited assumptions made visible.
Rebuild Hypothesis
Two different altitudes for the work and a clear reason for the direction you chose.
Napkin Spec 2.0
The outcome, inputs, quality bar, boundaries, exclusions, and human checkpoints.
Tested AI work system
One useful end-to-end workflow with a named owner and clear approval points.
Proof Pack
Five representative tests, expected results, observed results, failures, and changes.
Guardrail Card
Visible rules for data, human review, escalation, stopping, and recovery.
Impact Card
A before-and-after record of time, handoffs, rework, quality, and reviewer confidence.
Two-minute demonstration
A concise explanation of the work, the system, the evidence, and what the human still owns.
30-day operating plan
A cadence, maintained inputs, evidence to track, and a date to make the next decision.
Built for professionals with real work to change.
This is for you if...
- You own a recurring document, decision, research, or coordination workflow
- The work happens at least weekly or on a predictable recurring cycle
- You can bring public, synthetic, anonymized, or approved examples
- You want judgment and a tested system, not AI trivia
- You can complete the prework and use the system during the field test
This is NOT for you if...
- You want a general AI overview or a tour of tools
- You need production software or an enterprise integration
- Your use case involves high-stakes, regulated, or unsafe data
- You want to launch a startup product in one day
- You cannot bring a real workflow or test it after Build Day
Still unsure? Email me and I'll give you an honest answer.
Bring a Build Day inside your company.
A private Build Day gives a small team the same named method, direct support, and proof discipline as the public cohort. The work stays tied to outcomes and workflows your people already own.
If the team has not chosen the right starting point, the Audit can identify the strongest pilot before the build begins.
- The Premise to Practice Method for choosing and scoping AI work
- One bounded workflow per participant or working group
- Visible guardrails, approval points, and test evidence
- A leadership readout on what should expand, change, or stop
Why Rusty built this
Rusty Walters
Rusty is the founder of Now You're Technical and leads Data, Innovation & Intelligence at a global industrial technology company.
He works at the intersection of AI, work design, data, and adoption. His focus is helping nontechnical people use AI in consequential work without surrendering judgment or accountability.
Access is cheap. Judgment is scarce.
Build Days grew from a method Rusty uses to help people start with the outcome, question the work they inherited, and test a different path before they treat a tool as the answer. The goal is a useful tested pilot and better judgment, not the pretense that one workshop equals production implementation.
Not ready to apply?
Get the venue details and a few real examples first.
I will send the confirmed Jacksonville Beach venue, show you the kinds of workflows that fit, and tell you when the founding cohort is close to full.
A concise program overview
The October 3 schedule and venue when confirmed
Concrete workflow examples and fit guidance
A clear invitation to apply, with no pressure
Questions
Planning to ask your employer?
Use the prepared program summary, business case, and manager request.
Download the employer reimbursement packetHave another question? Email me. I respond personally.
Founding Cohort
Bring one part of your job. Learn how to see it differently.
Apply with one recurring workflow. Leave with a tested rebuild, the evidence behind it, and a method you can use again.
The Jacksonville Beach venue, participant terms, and staffing plan will be confirmed before payment opens.
Questions? Email me. I respond personally.