Understand the work before adding another role or system.
See what your HR team does, what needs human judgment, and what your existing systems can support before committing to another hire or tool. Work Architecture examines the work beneath roles and headcount so you can explain what should change and why. Verkitecture™ is Verk Vibe’s method for doing it.
Jon Orozco leads the work through the HR Work Architecture Sprint, an engagement of ten active working days for one HR function, beginning after the required inputs are ready.
Who it is for
Work Architecture fits a team facing a planned HR hire, a system purchase, an Ai mandate with no baseline or a scaling model it does not have. The Sprint is built for organizations of roughly 250 to 1,500 employees with an established HR team and technology stack.
If the HR team is one or two people, or the real request is to configure software, a Sprint is the wrong instrument, and the Fit Conversation will say so.
Roles are containers. Work is the content.
Every HR role is a bundle of activities that accumulated over time. Some produce outcomes the business needs. Some are legally required. Some were inherited from a system that no longer exists, a manager who left, or a process nobody redesigned when the company doubled.
Headcount decisions, technology purchases, and Ai initiatives all treat the bundle as fixed. Work Architecture opens it.
Start with the work, not the org chart.
The five lenses
01
Work
What work is actually being done, why, and what outcome does it exist to produce?
02
People
Which of it requires human judgment, and who is the right owner at the right level?
03
Technology
What should the systems you already pay for be handling, and where can automation or Ai help?
04
Economics
What changes financially, at which level, and when?
05
Readiness
Can the organization actually execute the change in the next 90 days?
Examine the work and the people responsible for it before considering technology. Then assess the financial implications and the organization’s readiness to act.
Three kinds of work
- Human Work
- Requires judgment, discretion, trust, or accountability the organization will not delegate to a system. Investigations, difficult conversations, decisions with legal or reputational weight. This work is named and protected, not squeezed.
- Machine Work
- Rule-based, repeatable, already within reach of the systems you own. Reconciliation, routing, reminders, record updates, standard reporting. Most of it is done by hand because nobody configured the alternative.
- Collaborative Work
- A person owns the outcome and a system does the heavy lifting. Drafting, summarizing, scheduling, first-pass analysis. This is where Ai belongs when it belongs anywhere, with a named human accountable for the result.
What can happen to an activity
Eliminate
The activity produces no outcome anyone needs.
Simplify
The outcome is needed. The current path to it is longer than it has to be.
Standardize
The same work is done three different ways by three different people.
Centralize
Scattered effort belongs with one owner who does it well.
Delegate
The work sits above the level it requires, and someone closer should own it.
Automate
Rules are clear, exceptions are rare, and a system you own can run it.
Augment
A person keeps the decision while a system carries the drafting or the first pass.
Consolidate
Two tools, two vendors, or two processes are doing one job.
Retain
The work is correct as it stands. Leave it alone and say so.
Redesign
The activity exists because the surrounding process was never rebuilt.
Evidence
Three sources, tested against each other rather than taken one at a time.
- Reported Work
- What employees say they do.
- Operational Evidence
- Tickets, systems, transactions, logs, reports, calendars, inboxes, forms, approvals, vendor activity.
- Leadership Expectation
- What leaders believe the function should be doing.
When the three disagree, the disagreement is recorded, not smoothed over. A discrepancy may reveal hidden work, duplicate work, inconsistent process, poor data, or a faulty leadership assumption.
Nobody is presumed dishonest. Missing evidence becomes a documented limitation, never silent certainty.
Three levels that never mix
Level 1
Released Capacity
Hours of work removed or reassigned. Real, useful, and not savings.
Level 2
Cost Avoidance
A credible future cost does not occur. Supporting growth without the hire you had planned, for example.
Level 3
Realized P&L Impact
Payroll, contractor, agency, overtime, consulting, software, vendor, or temporary-labor expense actually changes, counted from the date it changes.
Hours released are not savings until something changes financially.
One economic event lives at exactly one level, so the same dollar is never counted twice.
Readiness
Every recommendation is scored on six dimensions. The source of every score is shown.
- Technical capacity
- Operational capacity
- Change capacity
- Decision capacity
- Leadership sponsorship
- Resource availability
| Value | High readiness | Low readiness |
|---|---|---|
| High value | Do Now | Build Capability First |
| Low value | Optional Quick Win | Do Not Prioritize |
Questions about Work Architecture
- How is Work Architecture different from a headcount review?
- Work Architecture starts with the activities inside roles, not the roles themselves. It tests what employees say they do against operational evidence and leadership expectation. Each activity then gets a disposition such as eliminate, simplify, automate, augment or retain. Missing evidence is recorded as a documented limitation.
- Are hours saved the same as dollars saved?
- No. Work Architecture keeps three levels apart: released capacity, cost avoidance and realized P&L impact. Hours released are not savings until something changes financially, and one economic event is counted at exactly one level.
- What does the Sprint cost and how long does it take?
- The Sprint runs ten active working days for a fixed fee set in the proposal before the start gate. There is no hourly billing and no guarantee of savings. The ten days begin only when the five start-gate inputs are in hand, including the HR org chart, a technology inventory and booked diagnostic interviews.
- Who delivers the work?
- Jon Orozco, Verk Vibe's founder and fractional CHRO, runs the interviews, the analysis and the readout. The Sprint is delivered by one person. A Fit Conversation with Jon comes first, and he reads every request personally and replies within two business days.
Next step
Make the next decision with a clearer picture of the work.
Bring the staffing, systems, or Ai decision you are facing. Talk through what you need to understand, or review how the method runs as a Sprint with ten active working days after the required inputs are ready.