Premise&PracticeStart a conversation

PB Public Build Day / Jacksonville founding cohort · Saturday, October 3, 2026

Bring the work.
Build a better way.

Don't just learn AI. Rebuild Your Work Around It.

Bring one recurring part of a job, side venture, personal operating system, or team. Use the Premise to Practice Method to question the old path, build a working version, and prove it with real evidence.

Apply for the cohort ↗All public Build Days ↗

10 paid seats · $795 · Jacksonville Beach, Florida · Venue confirmation pending

BUILD NOTE / JAX-01STATUS: READY TO TEST

THE INHERITED PATH

  1. 01 Gather
  2. 02 Format
  3. 03 Draft
  4. 04 Handoff
  5. 05 Rework
REBUILD AROUND THE OUTCOME

IN PRACTICE

Frame→Build→Prove
AI changes the path.
You still make the call.
01THE PREMISESTART WITH THE WORK

A faster artifact is not a changed practice.

Most people point new tools at old work.

You can make the current report, deck, or handoff a little faster. The more consequential move starts one step earlier: naming what the work is for and deciding whether the inherited path still deserves to exist.

02PREMISE TO PRACTICEMETHOD / V1.0

Question it.
Build it.
Prove it.

You learn the method by using it on work you already own. The awkward questions show up while there is still time to answer them.

  1. 01ASSUMPTION

    Find the old premise

    Name the outcome, the inherited path, and the belief that made the current work seem inevitable.

  2. 02REVISION

    Rewrite the work

    Design a better path around what people and AI can do now. Keep the judgment. Remove inherited friction.

  3. 03WORKING VERSION

    Build it close to reality

    Make the smallest useful version that can survive real inputs, real boundaries, and the person who has to use it.

  4. 04EVIDENCE

    Prove it in practice

    Test normal work, edge cases, and failure. Keep what helps. Change what does not.

03BRING REAL WORKONE RECURRING WORKFLOW

What could you rebuild?

The best project is not the flashiest one. It is the recurring workflow you will use again next week.

01DECISION

Turn scattered inputs into an evidence-linked brief with a clear human call.

02INTAKE

Clarify requests, surface what is missing, and reduce the back-and-forth before work begins.

03REPORTING

Assemble recurring inputs, draft the narrative, and flag the exceptions that deserve attention.

04FEEDBACK

Turn comments into evidence-linked themes, decisions, and an action queue.

05MONITORING

Track a defined signal and surface only the change that matters.

04THE PROGRAMBUILT TO SURVIVE THE ROOM

One Build Day.
Enough structure to make it stick.

The work is scoped before the room, tested during the day, and used afterward.

  1. 01
    SCOPE CLINIC

    75 minutes · virtual

    Choose the work, question the inherited path, and cut the idea to a buildable scope.

  2. 02
    BUILD DAY

    Full day · Jacksonville Beach

    Build the chosen path, test the edges, and document one bounded AI work system.

  3. 03
    PROOF REVIEW

    60 minutes · virtual

    Return with real usage, repair weak points, and decide the next move.

  4. 04
    ADOPTION CLINIC

    60 minutes · virtual

    Measure what persisted and choose whether to expand, revise, maintain, or stop.

05THE PROOFLEAVE WITH THE WORK

Not a certificate.
A working version.

  1. 01

    A visible before-state and rebuild hypothesis

  2. 02

    A working AI-supported system for one recurring workflow

  3. 03

    Five representative tests with observed results

  4. 04

    A guardrail card for data, review, escalation, and recovery

  5. 05

    A before-and-after impact card

  6. 06

    A 30-day operating plan you can use after the room

GOOD FIT / YES

You own recurring work that deserves a better path.

  • You can bring safe examples and test the result afterward.
  • The work may come from a day job, side venture, personal system, or team.
  • You want judgment and a working system, not an AI overview.
  • You can attend the virtual clinics and the in-person Build Day.

NOT THIS TIME / NO

You need production software, regulated data, or a tool tour.

  • This is not a production implementation engagement.
  • Do not bring confidential, regulated, or unsafe data.
  • You need one real workflow you can use after the event.

PRIVATE BUILD DAYS / TEAMS

Need a Build Day for your company?

The Jacksonville event is open to individuals. Private Build Days bring the same method inside one company and apply it to the workflows your team already owns.

Explore team Build Days ↗
06YOUR FACILITATORRUSTY WALTERS
WORKING BELIEF

Access is cheap.
Judgment is scarce.

Rusty Walters 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. Build Days grew from a method he uses to help people start with the outcome, question inherited work, and test a different path before treating a tool as the answer.

07GET THE DETAILSNO PRESSURE / JUST THE FACTS

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

08QUESTIONSTHE PRACTICAL DETAILS

Ask the awkward questions now.

The program is practical, bounded, and built around work you can test safely.

EMPLOYER SUPPORT

Planning to ask your employer?

Use the prepared program summary, business case, and manager request.

Download the packet

Have another question? Email me. I respond personally.

ONE REAL WORKFLOW→ONE WORKING VERSION

Bring the work.
We'll build from there.

Apply for the founding cohort ↗

Saturday, October 3, 2026 · Jacksonville Beach · 10 seats · $795

Jacksonville Public Build Day | Premise & Practice