Skip to main content

Navigation

  • Client impact
  • Writing

AI Solutions

  • AI Systems
  • AI Development

Software teams

  • Design Systems
  • Product Design & Engineering
  • API Platforms
  • View all services for software teams
Get in touch
  • AI Systems

    Model-agnostic AI systems and agents that do real work

    AI Development

    Custom apps and tools built with AI-enabled engineering

  • Design Systems

    Depth of experience that few can match

    Product Design & Engineering

    Experts in cross-functional collaboration

    API Platforms

    Node.js, React, & GraphQL at scale


    View all services for software teams
  • Client impact
  • Writing
  • Contact

Method / Playbook · 3 min read

Activity Mapping

Activity mapping is a way to dynamically capture, and work on, product requirements in a format that’s more useful than a static document.

Prep time: 10 minutes · Duration: 1-2 hours · Participants: 3-4

Introduction

Activity mapping is a way to dynamically capture (and work on) product requirements in a format that’s more useful than a static document.

Activity Maps are comprised of:

  • all jobs a user should be able to complete via the app or product (e.g. “view account balance” , “view payment history”)
  • activities that group related jobs by a common theme (e.g. “manage account”)

The combination of jobs and activities should be an accurate representation all of the in-scope work the team needs to deliver. In this regard, the process of mapping can help bring increased clarity around scope items that may not have been captured in the Kickoff or related product specification documentation efforts. We like to think of it as an evolution on a typical “product requirements” document – activity maps are more human friendly, and can double as a project management tool.

People & participants

Activity Mapping is often (but not always) driven by the UX/Design Lead, involving close collaboration with other members of delivery team, stakeholders, and SMEs.

Once mapped, activities form the basis of the designer’s TODO list.

Tracking tasks with the Activity Map

The utility of Activity Maps increases when properties such as progress and assignees can be related to jobs. Tools such as Notion, Airtable, Github Projects make it possible to achieve this so that the map is both:

  • a representation of all the jobs that are in scope
  • the project status of all jobs (user jobs also double as designer tasks – who’s doing it, and how it’s going)

If your project has a lot of engineering elements, you’ll probably want to capture engineering tasks in a separate resource, or keep design task management in the same place you do engineering tasks, and retain the simpler form of the activity map just to ensure that all activities are accounted for in the designs.

Instructions

Preparation

Create an Activity Map resource in a Kanban-friendly tool like Notion, AirTable or GitHub Projects. The tool should let you to create a board of page and populate it with custom fields so that can display the jobs by progress as well.

Method

  1. In working sessions, define the core activities and jobs that the product supports where:
    1. Jobs are discrete tasks a user performs to fulfil an activity. E.g track time
    2. Activities group jobs into a related set. E.g. manage timesheets
  2. As you define jobs and activities, discuss and flag which items should be in scope.
  3. Repeat until there is consensus that we’ve captured the scope of activities and jobs that need to be supported
  4. Optional: assign properties for progress, assignee, and priority if you want to also conduct project management ops with this artefact.

Example

An example of an Activity Map authored in Notion showing jobs grouped by activity, and with related assignees to complete the design of the job.An example of an Activity Map authored in Notion showing jobs grouped by activity, and with related assignees to complete the design of the job.

An example of an Activity Map authored in Notion showing jobs grouped by activity, and with related assignees to complete the design of the job.

Detail view of a single job showing references to design files, and other supporting information.Detail view of a single job showing references to design files, and other supporting information.

Detail view of a single job showing references to design files, and other supporting information.

Chat to the following people to learn more about this play:

Ronald Aveling avatarRonald Aveling avatar
Ronald Aveling

Designer with a soft spot for systems and structured content. Knows the difference between tofu and tempeh. Makes a damn good brunch.

Giselle Stidston avatarGiselle Stidston avatar
Giselle Stidston

Designer who loves learning about new problem spaces. Knows how to solve cryptic crosswords and has a knack for expressing things as diagrams.

Ben Derham avatarBen Derham avatar
Ben Derham

Software Engineer. Helping teams solve tricky problems. Will stop to pat your dog.

Get playbook updates

For updates on future playbook publications, subscribe to our newsletter.

Related plays

  • Process mapping

    Process mapping surfaces the movement of information and user interaction throughout a system in the form of a flowchart. It captures assumptions or current-state realities related to how the system works, and helps expedite alignment, design, and development,

    October 2024·2 min read
  • User journey mapping

    User journey mapping captures the steps a user takes to complete a specific task in the form of a flowchart. It surfaces assumptions about how the team expects a user to interact with the product, and highlights pain points and areas for improvement.

    October 2024·3 min read

We’d love to work with you

Get in touch

Footer

Thinkmill is a member of the Tech Council of Australia(opens in new tab).

AI Solutions

  • AI Systems
  • AI Development

Software teams

  • Design Systems
  • Product Design & Engineering
  • API Platforms
  • View all software teams

Client impact

  • Lyka
  • ELMO
  • Tiimely
  • Atlassian
  • Reckon
  • AnywhereWorks
  • View all client impact

Open Source

  • Keystone (opens in new tab)
  • Keystatic (opens in new tab)
  • React Select (opens in new tab)
  • Classnames (opens in new tab)
  • Manypkg (opens in new tab)
  • Changesets (opens in new tab)