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:
- Jobs to Be Done (JTBD) states the progress the user seeks, independently of any solution [2][3][7].
- Technological affordances state what the technology makes possible for that user [4].
- House of Quality logic from quality function deployment (QFD) supplies the structure for relating the first two systematically [1].
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 framing | What it cannot do alone | |
|---|---|---|
| Jobs to Be Done | Supplies 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 affordances | Supplies 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 logic | Supplies 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 Done | The progress a user seeks in a particular situation, stated independently of a particular solution. |
|---|---|
| Core job and job steps | The 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 affordance | An 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 case | Links 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]. |
| Workflow | The sequence or arrangement of work through which the job is done. A use case may reshape it, but it is not the same thing. |
| Touchpoint | A user interface together with a user action. |
| System interaction | An 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
- 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.
- 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.
- 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.
- 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.
- Read the matrix (see the final section): row patterns, column totals, and the roof.
- 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.
- 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:
- A1 Sonic replication: reproducing a preferred rig's sound without the original gear.
- A2 Distributed expertise access: drawing on rigs captured or created by others.
- A3 Rapid reconfiguration: changing and adapting sounds quickly, between and within songs and to the venue.
- A4 Configuration memory: storing and recalling tested settings.
- A5 Low-cost sonic experimentation: auditioning and refining alternatives in advance.
- A6 Contextual portability: reducing the weight, volume, and effort of moving the rig.
- A7 Workflow integration: consolidating setup and connecting to the venue's sound system.
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) | A1 | A2 | A3 | A4 | A5 | A6 | A7 | Traditional-rig baseline | Nano Cortex-enabled outcome |
|---|---|---|---|---|---|---|---|---|---|
| Select an appropriate rig for the engagement | 3 | 9 | · | · | 3 | · | · | Limited to owned, borrowed, rented, or venue gear | Select from owned, captured, or community-created rigs |
| Prepare the required tones before the gig | 3 | · | 3 | 3 | 9 | · | · | Physical components must be assembled and compared | Audition, refine, and retain more alternatives in advance |
| Reproduce a familiar or preferred rig | 9 | · | · | 3 | · | · | · | Original rig usually needs to be available and transported | Use a preferred rig representation without the original gear |
| Store the sounds needed for the set | · | · | 3 | 9 | · | · | · | Settings must be remembered, marked, or reconstructed | Store and retrieve tested configurations |
| Transport the rig to the venue | 3 | · | · | · | · | 9 | 3 | Multiple heavy and bulky components must be moved | Reduce weight, volume, transport effort, and exposure |
| Set up efficiently at the venue | · | · | 3 | · | · | 3 | 9 | Several devices, power links, and audio cables | Consolidate setup with fewer components and connections |
| Connect to the venue sound system | · | · | · | · | · | 3 | 9 | May require amp, cab, microphone, DI, or backline | Connect flexibly to FOH, monitoring, or amplification |
| Produce the correct tones during the performance | 9 | · | 3 | 3 | · | · | · | Tone depends on physical gear, settings, mics, and backline | Reproduce captured and configured tones consistently |
| Change sounds between songs | · | · | 9 | 3 | · | · | 3 | Several pedals or amp settings may need coordination | Recall prepared configurations quickly and deliberately |
| Change sounds within a song | · | · | 9 | · | · | · | 3 | Multiple pedal actions may be required | Use assigned controls for smoother real-time changes |
| Adapt the rig to the venue | · | · | 9 | 3 | · | · | 3 | Physical settings, routing, or mic placement readjusted | Adjust output, EQ, effects, and routing without a rebuild |
| Maintain tonal consistency across gigs | 3 | · | · | 9 | · | 3 | · | Sound varies with backline, mics, settings, and availability | Carry the same digital rig and settings across gigs |
| Manage tuning requirements | · | · | 9 | · | · | · | 3 | Retuning, extra instruments, or gear may be required | Use tuner and selected transpose functions with less disruption |
| Recover from equipment unavailability | 9 | · | · | 3 | · | 3 | · | Missing gear requires substitution or compromise | Substitute a stored digital representation for some gear |
| Minimize technical distraction while performing | · | · | 3 | 9 | · | · | 3 | Several independent components need monitoring and adjustment | Use tested settings and coordinated control to reduce distraction |
| Unweighted column totals | 39 | 9 | 51 | 45 | 12 | 21 | 36 | Structural 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.
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:
- Weight the rows. As in a full House of Quality, multiply each score by how important the job step is to users, elicited from interviews or a survey, before ranking affordances.
- Use the roof. Mark where affordances reinforce each other and where they pull against each other, since pursuing one may erode another.
- Re-score for other situations. The same affordances scored against other core jobs, such as composition and recording or practice, yield different use cases from one technology.
- Compare alternatives. Adding a competing technology as a further benchmark column turns the matrix into a basis for comparison.
- Test it with users. The matrix is a structured hypothesis. The scores come from judgment, so validate them before treating the ranking as a finding.
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
- 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
- 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.
- Ulwick, A.W. (2005). What Customers Want: Using Outcome-Driven Innovation to Create Breakthrough Products and Services. McGraw-Hill.
- 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.
- 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.
- Jacobson, I. & Cockburn, A. (n.d.). Use-Case Foundation (Version 1.1). Ivar Jacobson International. https://www.ivarjacobson.com/publications/use-case-foundation
- Strategyn. Jobs-to-be-Done Playbook and job-map materials.
- Object Management Group (2017). OMG Unified Modeling Language, Version 2.5.1. https://www.omg.org/spec/UML/2.5.1
- Neural DSP. Nano Cortex. https://neuraldsp.com/nano-cortex
