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.
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 |
Write down answers to these; each maps to a step that follows.
A software company with two products and a services arm might sketch:
Everything in the sketch has a step below. Start with the structure of the map itself.
Next: Understanding Workstreams.
Admin Onboarding - Setting up Users and Teams
Step 3 of admin onboarding — invite your people, give fellow administrators the Admin role, and create a team for every working group so later steps have someone to assign work to.
Admin Onboarding: Understanding Workstreams
Step 5a of admin onboarding — what a workstream is, how core and nested workstreams organize the Map Value module, and the two-level rule of thumb before you create any.