Challenge
A senior product manager in a Germany-based technology company was drowning in unclear Jira categories, underused dashboards, and weak reporting while managing web-app change requests, enhancements, and bugs. Basic Jira usage was not enough—components, filters, JQL, and multi-report dashboards needed to support daily decisions. The organisation needed a focused one-day intervention on real project data, not a generic admin tour, so ticket hygiene and visibility improved immediately after the session.
Why custom
Public Jira courses rarely coach against a single product manager’s live backlog shape. We ran ~95% practical demos on a Jira Cloud instance, working the delegate’s categorisation and reporting problems directly. Flexible pacing absorbed configuration confusion and a mid-day Meet delay. That project-specific coaching is what an off-the-shelf beginners class would not have delivered.
What we built
| Module | Focus | Labs |
|---|
| Ticket structure & components | Classify and prioritise change, bug, and enhancement work | 1 |
| Filters & JQL | Find the right work fast with practical queries | 1 |
| Dashboards & reporting | Multi-report views for progress and resolution timelines | 1 |
| Live workflow Labs | Apply patterns on real product scenarios | 1 |
Delivery
One live-online day, 1:1 format on Jira Cloud. A Google Meet access delay after lunch cost ~20 minutes; the agenda flexed. Extra clarification time covered custom fields and filters. Continuous Q&A and live troubleshooting kept the session applied. Templates, dashboard layouts, and email follow-up support extended learning after the day.
Results
- Delegate implemented clearer ticket categorisation in daily Jira operations
- Custom dashboards created for progress and resolution visibility
- Meaningful reports produced for on-hold, cancelled, and timeline views
Client impact
- Improved efficiency in ticket tracking for product change work
- Better visibility into team progress through custom dashboards
- Stronger data for decisions on resolution timelines and blocked work
Proof
Working on my real backlog made the difference—I left with dashboards and ticket structures I actually use.
Senior product manager
Frequently Asked Questions
Can this programme be adapted to our stack?
Yes. Jira Labs follow your issue types, components, and reporting needs. For product managers we emphasise backlog hygiene, JQL, and dashboards rather than deep admin topics unless those are in scope.
What is the minimum and maximum cohort size?
This session was 1:1. Similar product-focused Jira days work well for 1–6 delegates sharing the same project context. Larger groups need a multi-day workshop format.
Live online or in-person, and how do you decide?
This delivery was live online with a shared Jira Cloud instance. In-person is optional; online works well for 1:1 coaching when sandbox access is ready.
What lead time do you need from brief to delivery?
A one-day custom Jira session usually needs about one week of lead time to review sample workflows and prepare Labs. Same-week delivery is possible when Cloud access is already granted.
Do you build custom Labs, or use standard ones?
Labs are custom and mostly practical demos on your patterns. We do not rely on generic sample projects when your live categorisation problems are the learning material.
How is training effectiveness measured?
Effectiveness shows up as implemented ticket structures, working dashboards, and reports the delegate can regenerate without coaching. We ignore attendance-style metrics for 1:1 days.
.webp)
.svg)
