GitLab Professional Services
Accelerate your software lifecycle with help from GitLab experts
Popular GitLab use cases
Enterprise Small Business Continuous Integration (CI/CD) Source Code Management (SCM) Out-of-the-box Pipelines (Auto DevOps) Security (DevSecOps) Agile Development Value Stream Management GitOpsGitLab Professional Services
Accelerate your software lifecycle with help from GitLab experts
Popular GitLab use cases
Enterprise Small Business Continuous Integration (CI/CD) Source Code Management (SCM) Out-of-the-box Pipelines (Auto DevOps) Security (DevSecOps) Agile Development Value Stream Management GitOpsThe main job is a process that you can map chronologically. The map reveals the process of completing the job from the executor’s point of view, not the buyer or customer perspective. The intent is to illustrate what the job performer is striving to get done at each stage in executing a job. A job map is not a customer journey, service blueprint, or workflow diagram. It does not reflect what a person does to discover, learn about, select, buy, and use a product or service. These activities are relevant to the buyer and purchasing process.
Note: It’s not about mapping tasks or physical activities, but about creating a sequence of smaller goals that make up the main job. Ideally, the job map will not include any means of performing the job.
From your interviews, create a sequence of stages in a visual representation that show underlying patterns of intent. As you map, think about what job performer’s subgoals are and what are the phases of intent that unfold as the job gets done. There is a template in Mural that you can use for this. The template uses the eight standard phases from Tony Ulwick’s Outcome-Driven Innovation (ODI) method:
Each stage should have a purpose and be formulated as a functional job. Avoid including emotional and social aspects in the stage labels, and avoid bringing in adjectives and qualifiers that indicate a need, like “quickly” or “accurately.” Strive to make the stages as universal and stable as possible without reference to the means of execution. Jobs are separate from solutions.
Consider these stages as more of a checklist than a prescriptive model. The point is to remember to cover all types of stages involved in executing the main job—before, during, and after. You’ll have to modify their labels as needed to describe your particular main job. Keep the labels short, ideally expressed as single-word verbs. The list below reflects some common verbs for each of the stage types in the universal job map.
Step 1 - Create a job map (Mural Template)
You might end up with fewer or more stages than eight. It’s also possible to include a loop for interaction or even a branch in the flow. The diagram you create should stand as a clear model for describing the process of performing the job that everyone in your organization can relate to.
Ideally, you will validate this job map with job performers. Talk through it with them. If the labels and/or divisions between stages need a great deal of explanation or seem to be confusing, rework them until it’s simple enough to be self explanatory.
Step 2 - Put the job map to use Job maps can be used to identify opportunities and ways to create new value. The job map ultimately defines the scope of your business/stage group. Align your solutions to it to spot gaps and opportunities. Compare alternative offerings and means of getting a job done for competitive insight. Prioritize areas within the job process to drive your service roadmap. Find opportunities that can be reflected in marketing campaigns and sales pitches.
To get started, ask yourself these questions: