Framing a Use Case: Jobs to Be Done, Affordances & the House of Frames

Why combine three lenses

Use cases are often drafted from a feature list or a loosely stated opportunity. Two familiar failures follow. Either the use case describes what the technology does without saying what progress a user is trying to make, or it describes a user need without saying what the technology newly makes possible. Each of three well-known perspectives covers one half of this problem, and together they give a use case a traceable rationale:

Applying House of Quality logic to jobs and affordances produces a compact visual that this entry calls the House of Frames: jobs as rows, affordances as columns, relationship strengths in the cells, interdependencies among affordances in the roof, and a comparison of today's way of working with the technology-enabled outcome alongside.

What each lens contributes

Role in the framingWhat it cannot do alone
Jobs to Be DoneSupplies the rows: a core job and the job steps through which a user makes progress.Says nothing about what is now technically possible, so it cannot by itself justify a solution.
Technological affordancesSupplies the columns: action possibilities the technology offers a particular user, which is a relationship between user and technology rather than a feature of the technology.Listed without jobs, affordances drift back into a feature inventory with no test of whether anyone needs them.
House of Quality logicSupplies the structure: WHATs (needs) against HOWs (means), a scored relationship matrix, a roof for interdependencies among the HOWs, and benchmark columns.Is a scoring discipline, not a source of insight. The quality of the output depends on the jobs and affordances entered.

The synthesis is a small adaptation of the House of Quality. Customer requirements become job steps, engineering characteristics become affordances, and competitive benchmarking becomes a comparison between the traditional way of doing the job and the technology-enabled outcome. Cells use a two-level scale, 9 for a primary relationship and 3 for a supporting one, with blank for no material relationship; QFD practice commonly also uses 1 for a weak relationship.

Working definitions

Much confusion in use-case work comes from terms that overlap. The distinctions below are the ones that proved necessary in practice.

Jobs to Be DoneThe progress a user seeks in a particular situation, stated independently of a particular solution.
Core job and job stepsThe core job is the overall progress sought; job steps are the stages through which it is accomplished. These replace the less precise "primary" and "sub" jobs.
Technological affordanceAn action possibility that the technology enables for a user and that supports one or more jobs. Where the enabling technology is AI, the term AI affordance applies.
Use caseLinks one or more jobs with one or more affordances for a specific user in a specific situation. It describes how the user and the system collaborate, under the relevant conditions, to actualize the affordances and produce an observable result of value. A full specification covers the main success path and the relevant alternatives and failures, without committing to an implementation [5][6].
WorkflowThe sequence or arrangement of work through which the job is done. A use case may reshape it, but it is not the same thing.
TouchpointA user interface together with a user action.
System interactionAn exchange between components or systems that does not involve the user directly. Touchpoints and system interactions elaborate a use case; they are not the use case.

The key distinction is between the first and fourth rows: a job says what progress is sought, while a use case says how a specific user and a specific system collaborate to deliver it.

Framing a use case, step by step

  1. Fix the user and the situation. Name the core job for a specific user in a specific situation, then break it into job steps. These become the rows. Keep each step solution-neutral.
  2. Separate capabilities, affordances, and benefits. A capability is what the technology does; an affordance is what that makes possible for this user; a benefit is the value that follows. Columns should be affordances, not features.
  3. Score every job step against every affordance. Use 9 for a primary relationship, 3 for a supporting one, and leave the cell blank where there is no material relationship.
  4. Add the two benchmark columns. Record how each job step is done today (the baseline) and how it would be done with the technology (the enabled outcome). This is where the reshaped workflow becomes visible.
  5. Read the matrix (see the final section): row patterns, column totals, and the roof.
  6. Write the use case. State the actor, the situation, and the observable result, then list the supporting behaviors, marking which are always included and which extend the main use case only under particular conditions. Touchpoints and system interactions come after that.
  7. Recompute the totals from the final cells. Totals worked by hand drift as cells are edited. In the example below, two column totals were corrected after the matrix was reworked.

Worked example: the Nano Cortex on stage

The example applies the method to a compact guitar modeling device, the Neural DSP Nano Cortex [9], used by a performing guitarist. The analysis began as a comparison of the device with an average guitarist's rig across live performance, composition and recording, and practice. It then moved from features to affordances, and the live-performance case was worked through in full.

The affordances. Seven technological affordances were identified:

The matrix. Fifteen job steps for the core job of performing live were scored against the seven affordances (columns A1 to A7, in the order listed above) and compared with a traditional-rig baseline.

Job step (WHAT)A1A2A3A4A5A6A7Traditional-rig baselineNano Cortex-enabled outcome
Select an appropriate rig for the engagement39··3··Limited to owned, borrowed, rented, or venue gearSelect from owned, captured, or community-created rigs
Prepare the required tones before the gig3·339··Physical components must be assembled and comparedAudition, refine, and retain more alternatives in advance
Reproduce a familiar or preferred rig9··3···Original rig usually needs to be available and transportedUse a preferred rig representation without the original gear
Store the sounds needed for the set··39···Settings must be remembered, marked, or reconstructedStore and retrieve tested configurations
Transport the rig to the venue3····93Multiple heavy and bulky components must be movedReduce weight, volume, transport effort, and exposure
Set up efficiently at the venue··3··39Several devices, power links, and audio cablesConsolidate setup with fewer components and connections
Connect to the venue sound system·····39May require amp, cab, microphone, DI, or backlineConnect flexibly to FOH, monitoring, or amplification
Produce the correct tones during the performance9·33···Tone depends on physical gear, settings, mics, and backlineReproduce captured and configured tones consistently
Change sounds between songs··93··3Several pedals or amp settings may need coordinationRecall prepared configurations quickly and deliberately
Change sounds within a song··9···3Multiple pedal actions may be requiredUse assigned controls for smoother real-time changes
Adapt the rig to the venue··93··3Physical settings, routing, or mic placement readjustedAdjust output, EQ, effects, and routing without a rebuild
Maintain tonal consistency across gigs3··9·3·Sound varies with backline, mics, settings, and availabilityCarry the same digital rig and settings across gigs
Manage tuning requirements··9···3Retuning, extra instruments, or gear may be requiredUse tuner and selected transpose functions with less disruption
Recover from equipment unavailability9··3·3·Missing gear requires substitution or compromiseSubstitute a stored digital representation for some gear
Minimize technical distraction while performing··39··3Several independent components need monitoring and adjustmentUse tested settings and coordinated control to reduce distraction
Unweighted column totals3995145122136Structural relationship strength, not validated importance or ROI

9 primary relationship   3 supporting relationship   · no material relationship. On a narrow screen, scroll the table sideways to see the last two columns, which compare the traditional rig with the Nano Cortex.

House of Frames for the use case Perform live reliably with a portable digital rig: fifteen job steps against seven affordances, with an affordance-relationship roof, baseline and enabled-outcome columns, and corrected column totals.

Figure: The House of Frames for the live-performance use case (the figure labels the device "Cortex Nano"; select the image to open it full size). The diamonds in the roof mark affordance complementarities and dependencies.

The framed use case.

Use case
Perform live reliably with a portable digital rig.
Primary actor
Performing guitarist.
Situation
Preparing for, traveling to, setting up for, and completing a live engagement that requires appropriate and repeatable guitar sounds.
Observable result
The guitarist completes the engagement using appropriate, repeatable sounds with less equipment burden and technical disruption.
Included behaviors
Prepare performance sounds (which itself includes accessing captured rigs, auditioning alternatives, and storing configurations); deploy the rig at the venue; integrate with the venue sound system; recall and change sounds.
Extending behavior
Adapt the rig to venue conditions, which applies only when the venue requires it.
Other actors
The venue sound system and the cloud service holding captured rigs.

In UML terms [8], the first four behaviors are «include» relationships of the main use case, while venue adaptation is an «extend» relationship, because it applies only under particular conditions.

Reading and adapting the matrix

Read the rows first. A job step with no primary affordance is a job the technology does not address, and a use case should not claim it. In the example, every one of the fifteen job steps has exactly one primary affordance, which makes the mapping straightforward to defend.

Then read the columns. Unweighted totals give the order A3 (51), A4 (45), A1 (39), A7 (36), A6 (21), A5 (12), A2 (9). In this example, rapid reconfiguration and configuration memory carry most of the structural weight, which suggests that the use case is less about portability itself than about changing and recalling sounds dependably in the venue. Distributed expertise access matters mainly in selecting a rig, so it is better treated as a supporting behavior than as the center of the use case.

Treat the totals as structure, not importance. They count how many jobs an affordance touches and how strongly, and nothing more. Adaptations to consider:

For a hands-on version of this kind of framing, see Activity A-5, on moving from opportunities and pain points to a development scope, in Activities & Exercises. Its Step 2 applies the jobs, affordances and scoring approach described here, and carries the result into the use case sketch and the build, buy or borrow decisions.

References

  1. Hauser, J.R. & Clausing, D. (1988). The house of quality. Harvard Business Review, 66(3), 63–73. See also American Society for Quality, Quality Function Deployment (QFD), https://asq.org/quality-resources/qfd-quality-function-deployment
  2. Christensen, C.M., Hall, T., Dillon, K. & Duncan, D.S. (2016). Know your customers' "jobs to be done". Harvard Business Review, 94(9), 54–62.
  3. Ulwick, A.W. (2005). What Customers Want: Using Outcome-Driven Innovation to Create Breakthrough Products and Services. McGraw-Hill.
  4. Gibson, J.J. (1979). The Ecological Approach to Visual Perception. Houghton Mifflin. See also Norman, D.A. (1988). The Psychology of Everyday Things. Basic Books.
  5. Cockburn, A. (2001). Writing Effective Use Cases. Addison-Wesley. See also Jacobson, I., Christerson, M., Jonsson, P. & Overgaard, G. (1992). Object-Oriented Software Engineering: A Use Case Driven Approach. ACM Press/Addison-Wesley.
  6. Jacobson, I. & Cockburn, A. (n.d.). Use-Case Foundation (Version 1.1). Ivar Jacobson International. https://www.ivarjacobson.com/publications/use-case-foundation
  7. Strategyn. Jobs-to-be-Done Playbook and job-map materials.
  8. Object Management Group (2017). OMG Unified Modeling Language, Version 2.5.1. https://www.omg.org/spec/UML/2.5.1
  9. Neural DSP. Nano Cortex. https://neuraldsp.com/nano-cortex