Admin Onboarding - Configuring Your Work Model
Step 4 of admin onboarding — decide your workstreams, item type hierarchy, teams, statuses, and cadences on paper before configuring them, because some of these are expensive to change once items exist.
You now have an organization with people in it. Before you configure the data model, stop and sketch it. The next five steps each take a few minutes to click through, but two of them, item types and workstream structure, are costly to rework once work has been created against them. An hour with a whiteboard here saves a support ticket later.
What a work model is#
Your work model is the set of structures DevStride uses to organize every item:
| Decision | Where it ends up | How hard to change later |
|---|---|---|
| Core workstreams and how they nest | Map Value | Easy: drag and drop |
| Item type hierarchy (Epic → Story → Task) | Settings → Item Types | Hard once items exist |
| Teams (working groups) | Settings → Teams | Easy |
| Status collections (board columns) | Settings → Data Model → Item Statuses | Moderate: items move when a status is removed |
| Cadences (sprint length, planning increments) | Settings → Cadences | Moderate: boards already on a cadence keep their dates |
| Custom fields, tags, priorities | Settings → Data Model | Easy |
Questions to answer first#
Write down answers to these; each maps to a step that follows.
- What are the three to eight big things the organization delivers? Products, programs, client accounts, or functions. These become your core workstreams. Name them for the value, not the team.
- How do you break big work into small work, and what do you call each level? For a product team, perhaps Epic → Story → Task; for marketing, Campaign → Deliverable → Task. One hierarchy per kind of work is fine. These become item types. Include a level you might need later: you cannot insert one in the middle after items exist.
- Which groups of people pull from a shared queue? Each becomes a team, and later a folder and board in Plan Delivery. People can be on several teams.
- What stages does work pass through? New and Done are fixed; everything between them is yours. Teams with different flows can have different status collections.
- Does each team work in fixed periods? Two-week sprints inside quarterly planning, monthly cycles, or continuous flow. This decides which cadences to create and which boards will be cycle boards.
- What extra data must every item carry? Customer, cost centre, RICE score. These become custom fields; a flag you want to see at a glance is a tag.
Keep it shallow
Two levels of workstreams and three or four item types cover most organizations. Depth you do not use hides work rather than organizing it, and every extra level is one more thing to roll up.
An example model#
A software company with two products and a services arm might sketch:
- Core workstreams: Product A, Product B, Professional Services, Internal Operations.
- Item types: Module → Capability → Epic → Story / Defect for product work; Engagement → Milestone → Task for services.
- Teams: Platform, Mobile, QA, Services Delivery, Customer Ops.
- Statuses: New → In Progress → Review → Done for engineering; New → In Progress → Client Review → Done for services.
- Cadences: 12-week Program Increment with 2-week Sprints beneath it for product teams; monthly for services.
Everything in the sketch has a step below. Start with the structure of the map itself.
Next: Understanding Workstreams.