Explore the lesson here. Canvas holds your check-ins, submissions, feedback, and progress.

← Learning path

Unit 09 of 12

Prepare the solution for use

Can an intended user access, understand, and complete the bounded task?

Learn

By the end of this unit

  • Prepare an accessible release package with truthful scope, instructions, and an acceptance task.
  • Check preparation, review, handoff, and support against a resource allowance and a capacity limit.

Planned guided work including the short textbook read-and-apply: 83–133 minutes, plus other project work. This is a design estimate, not measured learner time.

How to read this lesson

The labels describe how to use a passage. Color does not prove a claim is true or that a response is correct.

  • Explain — Understand the idea.
  • Try / predict — Make a choice or prediction before the reveal.
  • Evidence — Inspect the named source or supplied data.
  • Worked reasoning — Compare the steps after your own attempt.
  • Caution — Check a limit, assumption or unsupported conclusion.

Each figure has its own local legend for the data. Blue selection outlines mark the current selection; other outlines are explained by each figure’s local legend. Selection is not a correctness judgment.

Explain

Turn a working prototype into a usable release

Your first version worked under test. Now prepare a limited release that another person can locate, understand, and use. A release can be a clearly organized file, an approved shared folder, a visual no-code form, or a supervised service. Public hosting and an autonomous agent are not required. Select the simplest format that fits the task and permitted information.

ReplyKit's release package includes the current source card, intake/review templates, twelve worked cases, a 30-minute handoff, and one revision. The coordinator keeps control of commitments. For another project, the package might be a research extraction sheet with source checks, a creative draft kit with usage instructions, or a community resource helper with an exception route. These are transfer examples; continue your existing capstone.

Original release card for a fictional limited ReplyKit pilot
FieldPrepared scope
User and responsible ownerA coordinator completes the task; the operations owner authorizes continued use and exceptions.
Access and startOne current working file; a Start page identifies the version, permitted fictional inputs, first task, and review role. A complete downloadable file avoids requiring a new account.
IncludedSource card, intake/review templates, twelve worked cases, a 30-minute handoff, and one revision.
LimitsNo live participant messaging, booking/refund actions, unlimited support, or guaranteed time savings.
Acceptance taskThe user locates the source, enters a permitted question, prepares a checked reply or exception note, and records the real status.
Access and recovery checkReadable headings, labeled fields, a text equivalent for figures, clear error/missing-input instructions, an accessible alternate format when needed, and a manual fallback.

Prepare within the available resources

Suppose a pilot has a $180 resource-value allowance: a planning boundary for combining assigned effort value and stated cash expense, not a sale price or an all-cash budget. Preparation takes 3 hours, review 1 hour, and handoff 0.5 hour: 4.5 hours. At an assigned $24/hour, that is $108 of valued time. Add $12 incremental tool expense: $120 of stated resource value used. The arithmetic is $180 − $108 − $12 = $60 unallocated resource value.

That $60 is not cash remaining, profit, or evidence that a person will pay. The $108 is valued time and may not be a cash payment. The model has not included every possible setup, accessibility, support, or maintenance requirement. Record those omissions before calling the allowance sufficient. A budget is one constraint; usefulness, quality, access, and consequences still matter.

If the same person has 15 hours available this month to prepare, review, and hand off complete packages, 4.5 hours per package permits three whole packages: 13.5 hours, leaving 1.5 hours. A fourth needs 18 hours and exceeds the limit. A large list of interested users does not create reviewer capacity.

See the decision

One more revision uses more than a line on the plan

Try / predict

Predict what an additional revision changes: resource allowance, support capacity, or both.

Supplied case

A fictional resource plan for preparing one version, instructions, acceptance task and supported handoff. The allowance combines valued time and stated cash expense; it is not a price or cash balance.

Per-release resource plan and a 15-hour support limit
MeasurePlanned scopeAdd a second revision
Resource-value allowance$180$180
Incremental cash expense$12$12
Preparation/review/handoff time at $24/hour4.5 hours /$1085.5 hours /$132
Unallocated resource value$60$36
Complete supported releases within 15 hours32
Worked reasoning

The additional hour consumes $24 of valued time, reducing the unallocated resource-value allowance from $60 to $36. It also reduces capacity from 3 to 2 complete supported releases. The same 15 hours hold three 4.5-hour releases with 1.5 hours unused, or two 5.5-hour releases with 4 hours unused; a third would need 16.5 hours and exceed the limit by 1.5 hours. Neither remainder is cash remaining or profit. This narrow scenario excludes setup and recurring costs, which still need separate estimates. Capacity does not establish that anyone can successfully use the solution.

Use it in your project: Name one extra request outside your release plan and show how it changes effort, resources and the support commitment.

Required textbook reading and application · about 18 minutes

Read, then apply one idea

Read only the passages listed here. Mathematical derivations, algorithms, code, and end-of-chapter exercises are not assigned. The time estimate includes the brief passage and one connection to your existing project update; reading the passage alone usually takes much less time. It is a planning estimate, not a timer.

2.3.3: Offline and Online Computation

David L. Poole and Alan K. Mackworth. Artificial Intelligence: Foundations of Computational Agents. 3rd edition. Cambridge University Press, 2023.

Read: Go to 2.3.3 and find the online roles list. Read the complete Users item, including its explanations of the input interface and why users need reasons for a recommendation. Stop at the next item, Sensors. The earlier sections 2.3.1 and 2.3.2, formulas, and other roles are not assigned.

Why this unit: Explains that users may not know which inputs are needed and require a natural interface and understandable recommendations.

14.1: Types of Resources

Michael Laverty and Chris Littel. Entrepreneurship. 1st edition. OpenStax, Rice University, 2020.

Read: Read the opening explanation and the first paragraph under Tangible Resources. Then read the opening paragraph under Intangible Resources. Skip equipment shopping lists, funding, patent/legal advice and linked activities.

Why this unit: Identify different resource categories before promising that a solution can be delivered.

Course connection: In this section, online means while the system is operating (at run time), not necessarily connected to the internet; offline means computation done beforehand. A release needs clear instructions, required inputs, a bounded purpose, a checkable output, and a route for help or stopping. An AI-generated explanation is another output to verify; it is not independent evidence that a recommendation is correct.

Course connection: The book introduces intangible resources through intellectual property, such as designs and brands. Our project plan also tracks time, permissions, knowledge, and support as broader operating dependencies; do not treat that list as the book’s accounting classification. A file or AI subscription alone does not supply those dependencies. The course resource allowance is an original planning example, not a textbook accounting measure.

Apply one idea: Choose one prompt for the brief connection in your existing project update.

  • Write a three-sentence first-use guide: who it is for, what input to provide, and what the person must check. Add one clear stop or escalation condition.
  • Identify one physical resource and one nonphysical operating dependency your release needs. If you identify intellectual property, label it using the book’s intangible-resource category. Name one requirement your estimate omitted.
Read this textbook section here

The official page below may include material before or after your assigned selection. The reader does not automatically scroll or crop to that selection.

Assigned selection — 2.3.3: Offline and Online Computation: Go to 2.3.3 and find the online roles list. Read the complete Users item, including its explanations of the input interface and why users need reasons for a recommendation. Stop at the next item, Sensors. The earlier sections 2.3.1 and 2.3.2, formulas, and other roles are not assigned.

Official textbook section ↗

Read this textbook section here

The official page below may include material before or after your assigned selection. The reader does not automatically scroll or crop to that selection.

Assigned selection — 14.1: Types of Resources: Read the opening explanation and the first paragraph under Tangible Resources. Then read the opening paragraph under Intangible Resources. Skip equipment shopping lists, funding, patent/legal advice and linked activities.

Official textbook section ↗

Add a brief connection to your existing project update: identify the book and section, explain one relevant idea in your own words, and show the decision it informs. This is part of the same update, not another assignment.

If the official reader is unavailable or inaccessible, use the original lesson explanation and worked example, apply the same question, and label that access alternative honestly. Report the problem through the course support route; do not claim to have read an unavailable text.

Optional further reading

IDEO.org Design Kit — Build & Run Prototypes ↗

Read the five short steps. Identify what your version helps you learn and how you will record feedback. For this capstone, the final prototype must also perform the bounded task; a mock-up alone is not the final deliverable.

Try

Try / predict

Correct an unsupported promise and a difficult start

The proposed Start page says: “Save 75% of labor costs with automatic service.” It hides the source card and does not explain where to enter a question. Identify one evidence problem and one usability problem before opening the worked revision.

A release statement and acceptance check that fit the evidence

“ReplyKit prepares a reviewed draft or exception note for one approved workshop policy. Begin with the source card, then enter a fictional question in the intake table. A person checks the draft before use. The package includes the working files, a handoff, and one revision; it does not change bookings or guarantee savings.”

The unchecked benchmark uses 75% less supplied processing time but contains three material errors. The reviewed comparison shows 12.5% less complete effort in the same set; neither measures a guaranteed reduction in labor expense. Put the source beside the working table, label the input, and ask a reviewer to complete an ordinary task and find the fallback without coaching. Record the assistance actually needed.

Check the planned release against the $180 allowance and 15-hour monthly boundary. Keep the $60 unallocated resource value distinct from the 1.5 hours remaining after three deliveries. They measure different things. If additional support is needed, update the resource estimate rather than silently assuming it is free.

Decision lab · practice with your Learning Companion

The release budget meeting

Account for money, staff effort, and capacity before committing to release.

Take the role of release planner. Commit to a decision, uncover evidence, revise your reasoning, then carry one action into Build. Use this as the unit’s reasoning rehearsal; reuse the response in your existing project update.

Open the AI Learning Companion section below this interactive lesson to enter this unit’s decision lab. Return here for Build. You can also use the complete reading route below.

Complete reading route · no AI service needed

Fictional teaching scenario. A separate fictional mini-case offers a $300 planning allowance expressed in resource value. Release needs $120 in tools and 5 staff hours valued at $24/hour. Choose what you report.

  1. $180 profit after tools
  2. $60 unallocated resource-value allowance
  3. $60 cash in the bank

Choose one and write why before revealing the evidence.

Reveal evidence and challenge
Supplied evidence
  • Resources: Tools: $120 cash. Staff time: 5 × $24 = $120 in valued effort.
  • Allowance: The $300 is a planning limit in resource value, not a sales receipt or cash account.
  • Capacity challenge: A separate workload check finds only 3 staff hours available before the proposed release date.

The resource arithmetic fits the allowance, but capacity does not fit the date. What would you narrow, delay, or reassign?

Compare with the worked reasoning
Worked reasoning

Total resource value is $240, leaving $60 unallocated. Actual new tool spending is $120; staff time valuation is not automatically another cash payment. The 5-hour need exceeds 3 available hours by 2 hours. Narrow scope, delay, or obtain approved capacity, then recheck quality and ownership. Budget fit alone does not establish release readiness.

Apply to your project: Name a release resource, its cash or time unit, its owner, and a capacity constraint you must resolve.

Write your initial choice, evidence-based revision, and project action in your own document.

Practice boundary

Practice records are not grades or Canvas submissions.

Build

Apply this step to your chosen problem. Cedar Desk is the supplied classroom case; keep one project throughout the course.

Add a release card the user can follow

For the same capstone, identify the user and responsible decision owner, current alternative, intended result, actual delivery format and access location, permitted inputs, included work, exclusions, acceptance task, support boundary, and next decision. For an appropriate personal project, you can be the user and decision owner.

Prepare a Start page and verify access with the intended reviewer. Use readable headings, meaningful field labels, accessible text for important figures, and a clear missing-input or error route. State any access issue and alternative format rather than assuming everyone can use the same interface. Record the version and what has actually been made available; a proposed link is not a deployed solution.

Put evidence beside material performance claims and keep uncertain benefits conditional. Check preparation, review, handoff, and support against the resources you actually have. Explain whether the current process or a simpler template could be sufficient. Next, introduce a bounded version to users and observe the first task.

Add your project evidence and reflection to the check-in in Canvas.

Your project record

Write here or use your own document. Notes stay in this browser; export a backup to keep them. Nothing is submitted automatically.

Finish

What will you carry forward?

Your Canvas check-in

A pilot has a $180 resource-value allowance. Preparation, review, and handoff use $108 of valued time and $12 cash expense. What does the remaining $60 represent?

Use the evidence from this lesson to explain your reasoning in Canvas. Continue with Canvas Next below; submit your check-in in Canvas.

The simulation and Learning Companion support practice. They do not submit work, record Canvas completion, or assign a grade.

A pilot has a $180 resource-value allowance. Preparation, review, and handoff use $108 of valued time and $12 cash expense. What does the remaining $60 represent?

In your project record, state what you decided, the evidence you used, and one uncertainty to test next. Explain the reasoning in your own words.

You can revisit any step. Completion records study progress; it does not confirm a submission, grade, or project quality.