Functional Architecture in People Practices

People practices often fail at the point where they are supposed to
integrate.

Recruitment does not connect cleanly to workforce planning.
Performance management does not connect cleanly to learning. Learning
does not connect cleanly to succession. Succession does not connect
cleanly to organisational design. Payroll, job grading, headcount,
skills, equity, capability, structure and cost reporting all sit close
to one another, but not always in a coherent system.

The result is familiar.

People teams work hard, but the organisation still experiences
fragments. Reports do not agree. Roles are unclear. Talent conversations
become subjective. Workforce plans are disconnected from budgets.
Learning is offered without a clear line to capability requirements.
Performance data says one thing, managers say another, and finance sees
a different version of the workforce altogether.

The problem is not always effort.

It is architecture.

The development of business solutions in the realm of people
practices requires an integrated framework if it is going to deliver
strategic impact. We often speak about integration, but we do not always
design for it. We buy systems, define processes, run projects and
improve practices, but the underlying functional architecture is
missing.

Without architecture, technology simply automates fragmentation.

What Functional Architecture
Means

Functional architecture is the design logic that explains how the
parts of a function fit together.

It is not primarily an IT concept.

It is not a workflow diagram.

It is not a software implementation plan.

It is the set of business rules, relationships, structures,
definitions and design choices that determine how a function thinks,
operates, reports and improves.

In people practices, functional architecture asks questions such
as:

What is a role?

How is work defined?

How are positions related to roles?

How are people attached to positions?

How do competencies, outputs, levels and rewards connect?

How does workforce structure connect to cost?

How do performance, learning, succession and talent decisions use the
same underlying logic?

How does the organisation design for the future rather than merely
describe the present?

These questions matter because the answers determine whether people
practices can integrate.

The Building Plan Before
the Building

Functional architecture can be compared to the architectural plan for
a building.

Before anyone starts laying bricks, the architect clarifies what is
being built, what options exist, how the parts relate, which constraints
matter and what the future use of the building should be.

The same principle applies to people practices.

If the design is not integrated, the outcome will not be
integrated.

You cannot build a beach hut and expect it to become a mansion
organically. You can renovate. You can extend. You can improve. But if
the original design does not carry the future, every improvement becomes
more expensive and less coherent.

People solutions need the same discipline.

Before designing a recruitment process, performance process, learning
catalogue or succession review, we must understand the architecture that
these practices will share.

Otherwise each practice develops its own definitions, measures,
forms, levels and exceptions.

At first this seems manageable.

Over time it becomes a system that nobody fully understands.

Why Finance Offers a
Useful Comparison

Finance gives us a useful example.

The finance world understands integration deeply. The relationships
between the general ledger, debits, credits, journals, control accounts,
cash flow, income statements, asset registers and balance sheets are not
left to chance.

There is design discipline behind the system.

There are standards.

There are definitions.

There are relationships between the parts.

There is a clear logic that allows organisations to analyse, track,
report and audit financial reality.

What is unique in each organisation is the specific general ledger
design: the account codes, cost centres, reporting structures and levels
of granularity through which the organisation understands its financial
life.

Finance would never leave this architecture entirely to the IT
specialist.

Technology supports the architecture.

It does not invent the meaning of the architecture.

People practices need the same maturity.

The equivalent of a people-practice general ledger is the integrated
design of work, roles, positions, people, capability, cost and
performance. Without it, HR reporting becomes a collection of extracts
rather than a coherent view of organisational reality.

Technology Cannot Repair
Silo Thinking

Many organisations try to solve people-practice fragmentation by
implementing a new HR system.

The hope is understandable.

A modern platform promises integration. It can hold recruitment,
onboarding, performance, learning, talent, succession, payroll,
analytics and employee data in one environment.

But software cannot miraculously hold together silo-based
thinking.

If the organisation has not decided how roles are defined, how
positions are managed, how competencies connect to work, how structures
connect to cost, and how talent decisions relate to future capability,
then the system simply becomes a more expensive version of the same
confusion.

The problem becomes hidden behind configuration.

Different modules use different assumptions. Data quality
deteriorates. Reports require manual reconciliation. Exceptions
multiply. Managers lose confidence. HR spends more time maintaining the
system than using it for insight.

This is why functional architecture must come before technology
configuration.

The people function must own the design.

IT can advise on platforms, data, integration, security and
implementation. But the meaning of the architecture belongs to the
function.

Work-Centric and
People-Centric Architecture

One of the first choices in people architecture is philosophical.

Does the organisation design around work first, or around people
first?

A work-centric architecture begins with the business model, strategy,
operating model, processes, outputs and capabilities required by the
organisation. It asks what work must be done, how that work is
structured, what levels of accountability are required, and what
capabilities the future organisation will need.

Only then does it attach people to the work in the most effective
way.

This approach is useful in medium to large organisations where
fairness, parity, structure, workforce planning, role clarity and cost
discipline matter. It does not ignore people. It clarifies the
organisational need before building people solutions around that
need.

A people-centric architecture begins with the capability, interests
and potential of individuals. Work evolves around people and what they
are best able to contribute. Roles may be fluid. Structures may be
light. Reward and responsibility may be more individually
negotiated.

This can work well in smaller, creative or founder-led environments
where unique capability is the main source of value.

It can also become politically difficult if the capability mix is
unclear, leadership is weak or the organisation grows beyond the point
where informal role design can carry complexity.

Hybrid architectures are common.

Most organisations need a disciplined work-centric foundation, with
carefully designed space for flexibility where unique capability or
creative work requires it.

The danger is not hybridity.

The danger is unconscious hybridity, where exceptions accumulate
until nobody knows which rules apply.

Tier One: Defining the Role
Grid

The first design tier is the generic role grid.

This is where the organisation makes principled decisions about how
work will be named, grouped, levelled and compared.

A role grid answers questions such as:

What types of roles exist?

How many levels of work are needed?

What distinguishes one level from another?

How much granularity is useful?

Which roles are genuinely different, and which are variations of the
same underlying work?

What accountability levels must be visible?

Without this tier, organisations end up with role inflation,
inconsistent job titles, unclear career paths and reporting that cannot
compare like with like.

The goal is not to make every role generic in a crude way.

The goal is to create enough common structure for the organisation to
understand work at scale.

Tier Two: Defining Role
Content

The second tier adds content to the role grid.

This is where outputs, competencies, grading, benefits,
qualifications, experience, technical requirements and other role
attributes are defined.

This tier is important because it connects role architecture to
practical people decisions.

Recruitment uses it to define requirements.

Learning uses it to identify capability gaps.

Performance uses it to clarify expected outputs.

Reward uses it to support fairness.

Career development uses it to show progression.

Workforce planning uses it to forecast capability needs.

If role content is inconsistent, every downstream people process
weakens.

People practices then become dependent on local interpretation rather
than shared design.

Tier Three:
Positions and Workforce Structure

The third tier moves from generic roles to positions in the actual
organisation.

A role describes a type of work.

A position locates that work in a structure.

This distinction matters.

An organisation may have a generic role called Business Analyst, but
several positions using that role across different departments, cost
centres, projects or regions. Each position may carry different
reporting lines, funding arrangements, location requirements or timing
implications.

Position management connects people architecture to workforce
planning.

It helps the organisation answer questions such as:

How many positions exist?

Where are they located?

Which positions are funded?

Which are vacant?

Which are critical?

Which are temporary?

How does structure connect to headcount and cost?

Without this tier, organisations struggle to reconcile HR data,
finance data and operational reality.

Tier Four: People
and Individual Capability

The fourth tier attaches people to the architecture.

This is where personal information, employment history, performance,
learning, potential, preferences, mobility, readiness, succession and
individual capability are connected to roles and positions.

This is also where people-centric practices become possible within a
work-centric foundation.

The organisation can now see not only what work exists, but who is
connected to that work, what capability they bring, what they are
developing, where they may move and which risks or opportunities exist
in the talent base.

This tier should be handled with care.

People are not merely data objects.

But without a well-designed people layer, decisions become anecdotal.
Talent reviews become personality debates. Succession becomes a list of
names rather than a view of readiness. Learning becomes a catalogue
rather than a capability response.

Good architecture helps people decisions become more humane because
they become more explicit, evidence-based and fair.

Tier Five:
Connecting People Architecture to Cost

The fifth tier connects people architecture to finance.

This is where positions, people structures, payroll, costing, cost
centres, budgets and financial reporting must align.

The connection is critical.

People costs are often one of the largest cost categories in an
organisation. Yet many organisations cannot easily connect workforce
design to cost visibility. HR knows headcount. Finance knows cost.
Operations knows work pressure. These views do not always reconcile.

When the architecture is aligned, the organisation can answer better
questions:

What does this structure cost?

What is the cost of vacant positions?

Where is overtime masking workforce design problems?

What capability investment is required for a strategic shift?

How does a restructuring affect cost, capability and delivery?

Where are people costs growing without corresponding value?

This integration reduces administrative effort and improves strategic
insight.

It also improves trust between HR and finance.

Designing for the Future

Functional architecture should not only describe the current
organisation.

It should help the organisation prepare for the future.

If strategy is shifting, the people architecture must be able to show
what capabilities, roles, structures and costs will be required. If
technology is changing work, the role grid must be able to evolve. If
the organisation is growing, the architecture must support scale. If the
organisation is simplifying, it must show where complexity can be
removed without destroying capability.

This is why architecture is strategic.

It is not an administrative exercise.

It is a way of making the future organisation thinkable.

Professional
Accountability in People Practices

People professionals should take ownership of functional
architecture.

This does not mean every HR practitioner must become a systems
architect. It means the people function must accept accountability for
the integrity of its own design.

The profession should be able to explain how roles, positions,
people, capability, performance, learning, succession, reward, structure
and cost fit together.

It should be able to defend the design choices.

It should be able to improve them.

It should be able to collaborate with finance, operations and
technology from a position of clarity.

When HR does not own this architecture, someone else will shape it by
accident: a software vendor, a payroll configuration, a finance report,
a local manager, a historical job-title convention or a series of
exceptions.

That is not good enough for a strategic people function.

Conclusion

Functional architecture in people practices is the discipline of
designing how the people system fits together.

It is the difference between a set of HR activities and an integrated
people capability.

It clarifies the relationship between work, roles, positions, people,
capability, cost and future strategy. It helps technology serve the
function rather than define it. It allows HR to move from process
ownership to system ownership.

The organisation cannot expect integrated people outcomes from
fragmented design.

If we want people practices to deliver strategic impact, we must
design the architecture before we ask the processes and systems to
perform.

The building must be planned before it is built.

And the people function must be willing to become the architect.