Practice Map — Business, Discipline, and AI

This map supplements the Reader’s Guide with practical tasks in business, discipline, and AI. For the longer arc, see the 90-Day Action Plan; the four weeks here are one adjustable experiment within that plan. You do not need to finish it before acting, or start English, a business, and an AI project at once. Choose one problem that exists this week and turn your reading into an action you can finish.

Choose a path for your current problem

These outputs are starting suggestions, not universal performance requirements. If caring responsibilities, shift work, or unexpected events take your time, reduce the number of tasks while keeping a clear definition of completion.

A four-week practice path

This is an adjustable schedule, not a promise of income or mastery in four weeks. Try two 25-minute sessions and one 10-minute review each week, or spread a week of work across a longer period.

Week one: establish your starting point

Fill in a Learning State for one problem. Save a baseline: explain something without AI, time an existing process, or ask a user about the last time a problem occurred. “Someone will probably need this” remains a hypothesis.

Week two: make the smallest useful version

Choose something you can demonstrate. For English, write an email with a real purpose; for a business, deliver a small service manually; for AI, produce a summary with traceable sources. When AI is involved, use an AI Task Brief to fix inputs, boundaries, and acceptance criteria. For a business idea, use a Startup Experiment to define the hypothesis and stopping rules. Complete one cycle first.

Week three: collect real feedback

Give the output to an actual user, or test yourself independently on new material. Record what the user did and where they struggled, beyond “looks good.” Test an AI project with missing information, conflicting sources, and tool failures. For a business experiment, record silence, rejection, and reasons for not returning.

Week four: decide what to keep

Use a Weekly Review to compare the baseline with current evidence. Decide whether to continue, reduce scope, change the method, or stop, and record why. Carry one valuable action into the next cycle. Stopping a disproven approach is progress too.

Use one evidence system across topics

A local folder is enough. There is no need to build a complex knowledge system first:

my-practice/
  state.md       Current problem, baseline, next action
  attempts/      Work, tests, and deliveries
  feedback.md    User feedback, errors, and sources
  review.md      This week's decision and where to resume

Keep only useful material. Obtain permission for other people’s information and remove unnecessary identifying details. When sharing work publicly, exclude customer materials, private conversations, and credentials.

Judge a record by two questions: can you resume tomorrow, and can you explain the decision a month later?

Template toolbox

The Rhythm Ledger manages weekly capacity and rhythm; the Consistency Plan specifies one action experiment. Shorten any template. If filling it in takes longer than doing the work, keep only the task, evidence of completion, and next action.

How to read the guide

Method chapters offer processes to try and test. Personal stories describe experience in a specific setting. Follow the sources to check external research and product information. Unless explicitly stated otherwise, example numbers, two-week cycles, and sample sizes are practical starting points, not scientific thresholds or business guarantees.

For background, read Entrepreneurship and My Story. When you are ready to act, return to your chosen path and finish your first piece of work.