A free PDF compiled by Thoughtworks pulls together a dozen practical techniques for thinking through the social consequences of the software you ship. The document, called the Responsible Technology Guide, runs about fifty slides and treats each method as a short, self-contained playbook: what it is, who wrote it, when to reach for it, and how it tends to behave in a real team setting.
The pitch is straightforward. Most teams know they "should" think about harm. They rarely have a format for doing it. The guide is essentially a shelf of formats.
Who should care
| Audience | Why it fits | How to start |
|---|---|---|
| Product teams in regulated sectors | Financial, health, or legal software carries explicit accountability | Run Consequence Scanning during refinement for any externally-facing feature |
| Consumer-facing product owners | Your users are not in the room; surprises are costly | Use Tech Tarot Cards as a pre-sprint provocation exercise |
| Public sector and civic tech | Public trust and equity are structural concerns | Walkthrough with Me surfaces systemic risks early |
| Agile/Scrum teams | You already have ceremony; these slot into refinement | Treat one technique as a refinement format, not a new meeting |
| Solo developers and internal tooling | Less applicable; your users are usually colleagues | Skip unless your tool reaches external end users |
What the three starter techniques actually do
Each highlighted method is a physical or printable artefact you bring into a room. None requires a new toolchain or a consultant.
Walkthrough with Me (from the Omidyar Network) is a deck of cards built around a researcher moving through different risk areas. The team uses the cards to walk a product plan end to end and surface hazards the spec never mentioned.
Consequence Scanning (originally from Doteveryone, now hosted by the Open Data Institute) is a workshop kit for uncovering second-order effects of a feature. Teams identify unintended outcomes and sketch mitigations before the code goes anywhere.
Tech Tarot Cards (by Artefact) deal in provocations rather than risks: unusual uses, edge-case users, what happens when the product gets overused. They push the room to argue with itself.
The common thread is uncomfortable in a useful way. None of these are tick-box reviews. They want a diverse group in the room and they want documented follow-ups.
Our analysis
For teams already running refinement, the appeal is obvious. Adding another meeting is a hard sell. The honest framing is that these are refinement formats, not standalone ceremonies. They slot into existing sprint rituals when a feature has real-world stakes: a new data export, an algorithmic ranking change, a chatbot with public reach.
The trade-off is facilitator skill. Cards do not run themselves. A team that grabs Walkthrough with Me and runs it cold will get a generic brainstorm. Teams that invest one sprint in learning the format tend to get specific, actionable worries written down—and that is the point.
The techniques work best where software reaches people who are not in the build meetings. Regulated industries, consumer apps, public sector, anything touching children or health: these are the obvious fits. Internal scripts, infrastructure tooling, one-off automation: the guide does not pretend every commit deserves a workshop, and neither should you.
Watch whether the techniques stay lightweight. The moment any of these decks requires a two-day certification, they are dead in most real teams. The guide's value is that it ships as a PDF and respects your calendar.
A worked example
Say you are a Product Owner about to start a sprint on a new "trending topics" feed for a news app. Pull the Walkthrough with Me deck into your refinement session. Spend twenty minutes walking the user journey card by card, with an engineer, a designer and a content moderator in the room. By the end you will likely surface things like recommendation-loop risk, the impact on smaller publishers, and how a bad actor might game the algorithm. Write each one as a backlog item with an owner. None of this replaces legal review. It does mean your sprint review is not the first time anyone has asked the question.
What to watch next
The guide packages a dozen techniques into a free fifty-slide PDF. Three are flagged as first steps: Walkthrough with Me, Consequence Scanning, and Tech Tarot Cards. If your team already runs retros, this is the next ritual worth trying. Pick one card set. Run it once. See what turns up.
Key takeaways
- The Responsible Technology Guide packages a dozen workshop techniques into a free 50-slide PDF available from the Thoughtworks website.
- Walkthrough with Me, Consequence Scanning and Tech Tarot Cards are the three recommended starting points.
- Treat them as refinement formats, not extra meetings, and pair each session with a clear follow-up owner.
- Reach for them when a feature can affect people who are not in the room; skip them for purely internal tools.
Frequently asked questions
Is the Responsible Technology Guide free to download?
Yes. It is available as a free PDF from the Thoughtworks website.
Do I need a facilitator to run these techniques?
In practice, yes. The guide describes formats; running them well still depends on someone who can keep the conversation specific and write the outcomes down.
How long does a typical session take?
The guide describes short workshop blocks rather than full-day events. Expect to budget at least an hour for a meaningful first run with a real team.
Are these techniques only for large product teams?
No, but they pay off most where the software reaches end users who are not in the build meetings. Internal tooling usually does not need them.
How does this fit with existing Scrum events?
Most naturally inside refinement and sprint review, when a story has visible external impact. They are not meant to replace retros or planning.