Current picture
- Reporting
- Three specialists report to the delivery lead.
- Positions
- Four existing positions in the example.
- Working relationships
- One delivery function.
DRYVN PEOPLE
Understand today’s structure. Explore what should change.
Organization design asks how work and responsibility should fit together. Start with the positions, incumbents, vacancies and reporting relationships you have; then ask whether a different structure would solve the problem. Dryvn’s structural records provide the foundation. The scenario views illustrated here are product direction.
Delivery lead
- Specialist A
- Specialist B
- Specialist C
Delivery lead
- North team leadNew position proposed
- Specialist AReporting line changes
- Specialist BReporting line changes
- South team leadNew position proposed
- Specialist CReporting line changes
- 3 existing positions moved
- 2 new positions proposed
The current delivery lead has three specialist positions. The proposed structure inserts two regional lead positions: specialists A and B report to North; C reports to South. Three existing reporting connections change and two positions are proposed.
Scenario comparison and execution are planned capabilities. These trees explain a design question; they do not change live records.
START WITH THE OPERATING QUESTION
An org chart shows a structure. Design asks whether it works.
A delivery function has three specialist positions reporting to one delivery lead. The question is whether two regional teams would make decision ownership clearer. Drawing two boxes is easy; deciding what those leads should own requires a business discussion.
First establish the current picture: which positions exist, which are occupied, who reports to whom and where responsibilities overlap. Treat a missing incumbent differently from a missing position.
Then state the design question in terms people can review. In this example: which decisions should move to a regional lead, and which responsibilities should remain with the delivery lead?
THE STRUCTURAL FOUNDATION
A job describes the work. A position gives it a place.
A job describes a kind of work. A position places that work in the organization, with structural relationships. An incumbent is the employment currently assigned to that position; a vacancy is a position without an incumbent.
Keeping these distinctions clear lets a team discuss its structure without using a person’s name as the definition of a role. A change of occupant does not, by itself, mean that the position disappeared.
Dryvn’s existing position and employment records support this foundation. A proposed structure still needs review of responsibilities, affected people and the changes that are actually authorized.
Position recordDS-02 · Delivery specialist
Job: Delivery specialist
- Earlier occupancyFirst incumbent
An employment is assigned to the position.
- Between incumbentsVacant position
The structural role remains without a current incumbent.
- Later occupancyNext incumbent
A different employment can occupy the same position.
Current position and employment records provide structural context. This illustration does not promise automated succession or scenario execution.
Delivery specialist position DS-02 belongs to the Delivery specialist job. Across three illustrative stages it is occupied, vacant and occupied again. The position is distinct from each person and employment.
Review the proposal in business terms.
Current pictureProposed alternativeReview needed
ReportingThree specialists report to the delivery lead.Three specialists report through two new regional leads.Which decisions move, and who remains accountable?
PositionsFour existing positions in the example.Six positions: four existing, two proposed.Who authorizes the new positions and their scope?
Working relationshipsOne delivery function.North and South teams within that function.How will cross-region handoffs work?
Proposed alternative
- Reporting
- Three specialists report through two new regional leads.
- Positions
- Six positions: four existing, two proposed.
- Working relationships
- North and South teams within that function.
Review needed
- Reporting
- Which decisions move, and who remains accountable?
- Positions
- Who authorizes the new positions and their scope?
- Working relationships
- How will cross-region handoffs work?
A PROPOSAL IS NOT AN IMPLEMENTATION
Keep a planning discussion separate from a live change.
The example proposes two new lead positions and three changed reporting relationships. It does not claim that those moves automatically improve capacity or reduce cost. The team still needs to examine responsibilities, workload and alternatives.
Assign someone to own the proposal, gather input from the affected managers and record the decision that is needed. If the proposal is accepted, agree the implementation scope, communications and the people responsible for carrying it out.
Side-by-side scenario editing, automated comparison, costing, design approvals and coordinated execution are planned capabilities in this story. They should not be treated as available controls in the current application. Use the waitlist or a discussion with Dryvn to confirm release scope.
FROM STRUCTURE TO WORKING PRACTICE
A new structure creates a change question too.
A reporting relationship on a chart does not explain a handoff to employees. People may need to understand which decisions they can make, where work goes and what support their managers will provide.
That is the connection to change management: consider the groups affected, the intended way of working and the evidence needed to understand readiness. It is complementary planning work, not an automatically generated change program.
Explore the structure solution for the organizational foundation, then the Change page for the wider product direction around adoption and follow-through.
QUESTIONS, ANSWERED
A few things to know before you choose.
How is organization design different from an org chart?
An org chart presents relationships. Organization design considers whether responsibilities and the way work flows are appropriate, and evaluates alternatives. A diagram alone does not resolve those decisions.
Why distinguish positions from people?
A position is part of the structure; a person and their employment are distinct records. A position can be vacant or occupied by different employments over time. That distinction keeps the structural role visible when the occupant changes.
Can I use the illustrated scenario without changing live data?
The trees on this public page are static, synthetic examples and cannot change records. In-product scenario planning and comparison are planned; do not infer an available sandbox editor from the illustration.
Does Dryvn automatically calculate scenario cost or impact?
No automatic scenario costing or impact computation is promised on this page. The illustrated proposal identifies structural questions for human review, not a calculated business case.
Which parts should we evaluate now?
Evaluate the current People, position, vacancy and reporting-relationship workflows with Dryvn. Confirm advanced organization-design availability separately before relying on scenario comparison, approval or execution.
A PRACTICAL NEXT STEP
Bring the question behind the chart.
Tell us what your current structure makes difficult and which alternative you want to understand. We will distinguish the available foundation from planned design workflows.