
AI can change workflows, skills, decisions, risks, dependencies, and customer expectations faster than an org chart can respond. This course begins with the invisible operating system underneath formal structure: work, decisions, handoffs, information flow, judgment, and accountability. You will learn to redesign how the organization actually functions before changing titles, layers, or reporting lines.
Use the Toolkit throughout the course to map real work, decision rights, handoffs, dependencies, informal authority, exception work, role bundles, accountability, spans, layers, and redesign options. You will also use it to apply the WORK framework, prepare for both guided practices and fictional cases, compare alternative organizational designs, and define evidence that should trigger future reconfiguration.
Reporting lines are only the visible layer of organization design. The real organization also includes decisions, informal authority, coordination, tacit expertise, exception work, escalation, and information flow. Learn why companies can change titles and boxes while preserving the same bottlenecks, decision delays, and hidden dependencies. The central principle is simple: redesign the work before you redraw the boxes.
Organizational problems rarely sit inside one box on the chart. Use systems thinking to examine boundaries, dependencies, handoffs, delays, feedback, and local-versus-system effects before changing structure. The goal is not to turn this into a systems-thinking course, but to recognize when removing a layer or changing a role simply moves coordination work, risk, or decision delay somewhere else.
Arcadia removes a management layer after introducing AI-enabled workflow tools and expects faster decisions. Instead, meetings multiply, approval loops persist, managers continue shadow coordination work, and one expert becomes the unofficial decision bottleneck. Diagnose whether the problem is excessive hierarchy, unclear decision rights, missing capability, workflow design, or unmanaged dependencies—and decide what structure actually fits the work.
AI changes roles by changing pieces of work, not by magically replacing entire jobs. Map what people contribute, what AI contributes, where handoffs occur, where review belongs, and how exceptions move through the workflow. Use this lecture to see role redesign as workflow redesign first. A new organizational structure should follow the work rather than forcing work into predetermined boxes.
Participation in a decision is not the same as authority over it. Clarify who generates information, recommends, reviews, approves, overrides, escalates, and remains accountable when AI contributes to organizational decisions. Apply these distinctions to role and structure design so authority does not become ambiguous after automation. Strong redesign makes decision rights visible instead of assuming reporting lines automatically answer who decides.
Map a fictional AI-enabled customer decision that crosses Product, Operations, Legal, IT, and Customer Support. Identify who supplies information, recommends, decides, approves, executes, reviews, and handles exceptions. Then uncover duplicated approvals, hidden informal authority, and an escalation path that bypasses the formal chart. Your output is a clearer decision-rights map showing what should be clarified, consolidated, distributed, or protected.
Human oversight has little value if people cannot actually question, correct, override, or appeal an AI-supported outcome. Examine meaningful human control through the sequence Question → Correct → Override → Appeal. Use this lens when redesigning roles involving consequential decisions so accountability remains practical rather than symbolic. The greater the consequence, the more explicit the authority and challenge path should become.
Jobs are bundles of tasks, decisions, relationships, judgment, accountability, and exception handling. AI may change only part of that bundle. Learn to distinguish what should be automated, augmented, centralized, decentralized, standardized, preserved as human judgment, redesigned, or removed entirely. The key question is not “Can AI do this job?” but “What work remains, and who should own it now?”
Decompose a fictional Operations Manager role containing planning, reporting, approvals, coaching, exception handling, customer escalation, analysis, and coordination. Classify each element as Automate, Augment, Keep Human, Centralize, Decentralize, Eliminate, or Investigate. Then rebuild the role with explicit decision rights, accountability, capability needs, escalation, and handoffs. Finish by checking whether you actually reduced work—or merely transferred it.
A redesigned organization still needs the capability to perform the work. Examine workforce choices through build, buy, borrow, automate, and protect decisions. Use this lecture to connect changing tasks and technology to skills, role coverage, capacity, and future workforce needs. The goal is not a full workforce-planning course; it is ensuring the proposed organization has the capability its new design actually requires.
Changing structure does not automatically change behavior. Informal norms form through leader behavior, peer responses, reinforcement, consequences, repetition, and social proof. Apply this to redesign by asking which old approval habits, escalation patterns, visibility rules, or power relationships will continue after the chart changes. The new structure can fail if people still behave according to the old organization’s unwritten rules.
Redesign competes for scarce people, time, management attention, technology, skills, and implementation capacity. Learn to identify the real constraint, compare competing priorities, make opportunity cost visible, and decide what should be funded, staffed, sequenced, reduced, paused, deferred, or stopped. Use this resource-allocation lens so the redesigned organization reflects realistic capacity rather than an ideal structure no one can actually sustain.
A strong organizational design should not require another full restructuring every time conditions change. Use Anchor → Map → Flex → Trigger → Reconfigure → Review to identify what must stay stable, which dependencies make the design fragile, where flexibility belongs, what evidence should trigger reconsideration, and how roles, decision rights, resources, or coordination can be reconfigured without losing direction.
Meridian’s AI scheduling and triage system reduces routine coordination but creates more complex exceptions, data-quality questions, cross-team escalation, and interpretation work. Supervisors absorb edge cases, analysts become informal system interpreters, IT gains de facto authority, and frontline employees handle explanation and correction.
Before entering the capstone Role Play, use the WORK method—Work, Ownership, Relationships, Keep / Change—to bring the course together. Diagnose what is actually happening before recommending another structural change. The goal is not to produce a prettier org chart, but to determine whether roles, decision rights, handoffs, accountability, or the structure itself should change.
Bring the course together through the WORK method: Work, Ownership, Relationships, Keep / Change. Revisit your Toolkit, Role Play feedback, and redesign decisions, then apply them to a real organization. The final question is not whether the new chart looks cleaner. It is whether work moves more effectively, authority is clearer, accountability is stronger, and the organization can adapt as conditions change.
This course contains the use of Artificial Intelligence.
Most organizational redesign starts with the org chart.
Change the reporting lines. Remove a layer. Widen spans. Add AI. Rename roles. Give teams more autonomy.
Then the strange part begins.
Decisions still wait for the same people.
Meetings multiply.
Former managers keep doing invisible coordination work.
AI changes tasks, but no one is quite sure who now owns the judgment, the exceptions, or the consequences.
The boxes changed.
The organization did not.
That is the problem this course is built to solve.
Redesign the work before you redraw the boxes
Organizational Redesign in the AI Era: Redesign Work First takes a different approach to organization design.
Instead of starting with hierarchy, you will learn to look underneath it.
You will examine the work people actually do, where decisions really happen, which handoffs slow everything down, where informal authority lives, what AI has genuinely changed, and what responsibilities quietly remain after automation.
Because the biggest redesign mistakes often look successful on paper first.
A flatter organization can create more meetings.
More autonomy can create slower decisions.
Automation can remove tasks while increasing exception work.
A new structure can preserve the exact same bottlenecks under different titles.
What will you be able to see that others may miss?
By the end of the course, you will be better prepared to recognize:
when the org chart is hiding the real operating system
when decision rights are unclear even though reporting lines look clean
when removing a layer simply transfers coordination work somewhere else
when AI changes a task but not the accountability attached to it
when one expert has quietly become the organization’s real approval bottleneck
when standardization, centralization, decentralization, or automation is being chosen because it sounds modern rather than because it fits the work
when a redesign needs adjustment before leadership launches another reorganization
The question is not “What should the org chart look like?”
The more useful question is:
How should the work actually work now?
You will use practical tools to examine roles, decision rights, handoffs, dependencies, human judgment, accountability, capability, layers, spans, and redesign options.
You will also work through realistic situations where there is no obvious “correct” structure.
Because good organization design is not about choosing flatter, leaner, more centralized, more decentralized, or more automated.
It is about matching the design to the work.
You will apply the course, not just watch it
The course includes a practical Organizational Redesign Toolkit, guided exercises, fictional cases, and an interactive Role Play where you must diagnose a restructuring that looked right on paper but made decisions slower.
You will practice making the kinds of tradeoffs leaders face when:
AI changes part of a role but not the whole role
accountability becomes blurred
formal authority and real authority diverge
coordination work survives a restructure
teams disagree about who can decide
leadership is already considering another reorganization
This course is for you if...
You are involved in organizational redesign, AI transformation, operations, HR, workforce strategy, leadership, change, or restructuring—and you want to make better design decisions before another round of boxes, titles, and reporting lines gets locked in.
You do not need an organization-design background or technical AI expertise.
You do need a willingness to question assumptions such as:
Flatter is always faster.
Automation means fewer roles.
Formal authority equals real authority.
If the chart changed, the organization changed.
Those assumptions can become expensive.
The earlier you see the hidden design problem, the easier it is to correct.
About your instructor
I’m Crystal Hutchinson, founder of Pursuing Wisdom Academy.
Since 2018, I have taught more than 100,000 learners across business, leadership, technology, cybersecurity, compliance, privacy, and responsible AI.
My approach is practical and decision-focused. I am less interested in telling you what the organization of the future is supposed to look like than in helping you make stronger choices about how work, authority, capability, accountability, and structure should actually change.
Before you redraw the boxes...
Find out whether the work has actually been redesigned.
Enroll now and learn how to redesign the organization beneath the org chart.