Detours / things that somehow became my job
NOT IN THE ORIGINAL BRIEF

Wait.
You do
that too?

Apparently, yes. My career has a habit of wandering into systems, IT, process design, self-service, data, training and communication — usually because something needed doing and I was curious enough to get involved.

Job
description
A useful starting point. Not always a reliable prediction.
RECURRING CAREER EVENT
“Since
you’re
here…”
And that is how the interesting bits tend to start.
HRIT SUPPORTintranet platformWORKFLOWSDATACHATBOTSTRAININGPROCUREMENTPROCESS DESIGNSELF-SERVICE HRIT SUPPORTintranet platformWORKFLOWSDATACHATBOTSTRAININGPROCUREMENTPROCESS DESIGNSELF-SERVICE
A small theory

The detours weren’t really detours.

They look random if you organise a career by job title. They make more sense if you organise it by problems I kept being drawn to: things that were manual, unclear, fragmented, hard to find, or held together by someone remembering what to do next.
CAREER MAP / definitely not to scale
START HEREHR operationsRecruitment, onboarding, employee administration.
DET0UR 01AutomationBecause doing the same admin repeatedly started to feel suspicious.
DET0UR 02intranet platformBecause information is not self-service if nobody can find it.
DET0UR 03 / COVIDIT supportDevices, Microsoft 365, network equipment, vendors. Yes, still technically in HR.
DET0UR 04System developmentWorkflows, prototypes, data integrity, permissions, notifications.
DET0UR 05Self-service + chatbotPart systems problem. Part information problem. Part communication problem.
ALSO, SOMEHOWTraining + guidesBecause a solution nobody understands is not much of a solution.
Maybe the wandering
was following something.
Detour / who owns the seams?

“That’s not your scope.”

I used to get chastised for wandering into other people’s scopes — both inside and outside HR. Eventually I realised I wasn’t wandering randomly. I was following the friction across organisational boundaries because the person experiencing the process did not stop at the boundary.

The scope ended.
The friction didn’t.
ONBOARDING / FIVE OWNERS, ONE EXPERIENCE
HRHR onboarding completed
ADMINStaff pass issued
ITEquipment + accounts ready
MANAGERLocal setup completed
FACILITIESWorkspace / access ready
5 FUNCTIONS / 5 × COMPLETE ✓
BUT
Who checked whether the onboarding was actually complete?
THE ORGANISATION SAW
functions.
THE OFFICER EXPERIENCED
one organisation.
OFFBOARDING / PEOPLE FIRST, APPARENTLY

A physical integration layer.

Each department’s clearance requirement can make perfect sense on its own. Put them together and the officer can end up physically walking the organisation’s fragmentation from desk to desk.

STAFF CLEARANCE FORM / PLEASE OBTAIN ALL SIGNATURES BEFORE DEPARTURE
HRCLEAREDrecords / handover / signature
ITCLEAREDdevice / accounts / signature
ADMINCLEAREDpass / keys / signature
FINANCECLEAREDclaims / advances / signature
FACILITIESCLEAREDaccess / property / signature
OTHER???someone will remember
The employee should not have to become the integration layer between our systems.
I wasn’t wandering outside my scope.

I was following the friction.

The end-to-end experience did not belong neatly to HR, Admin, IT, Finance or any other single function. So if the friction crossed the boundary, I crossed it too.

Not because every adjacent function had become “my job”. Because somebody still had to see the whole thing.

↳ across the boundary where everyone else’s scope stopped.
THE BIGGER PRINCIPLE

Absorb friction.

The employee should not have to absorb the complexity of our organisational structure. The organisation should.
01Automate the process.Remove machine-like work from the human.
02Simplify the system.Reduce the organisational complexity they have to carry.
03Clarify the message.Make the next action understandable.
04Protect the human interaction.Keep the effort that actually matters.
↳ THE LAST ONE IS WHY WE DID THE OTHER THREE.
Selected evidence

Things I wasn’t necessarily hired to become.

Not a collection of hobbies. These are examples of responsibilities and projects that grew around the core HR work.

FILE 001 / THE ACCIDENTAL IT DEPARTMENT

HR person.
Also doing IT.

During COVID-19 at a social service agency, I concurrently supported end users, procured and set up laptops and Microsoft 365 accounts, helped maintain network equipment and coordinated external IT vendors.

WHAT THIS TAUGHT ME → technology problems are often user problems wearing a different outfit.
FILE 002 / THE INTRANET

Apparently I build places for information to live.

Implemented an organisation-wide intranet platform intranet to centralise HR resources and reduce recurring queries.

ESTIMATED IMPACT → ~50 MAN-HOURS / MONTH RECOVERED
FILE 003 / THE SYSTEM BUILDER BIT

Excel was doing too much. So I started designing the alternative.

Identified scalability and data-integrity issues in contract lifecycle tracking and designed a purpose-built replacement prototype around role-based permissions, notifications and existing approval flows.

SCALE → CONTRACT LIFECYCLE FOR 130 OFFICERS
FILE 004 / THE COMMS-BUT-NOT-COMMS BIT

Make the next action obvious.

Created HR guides, training materials, process maps and user-facing resources alongside system and process work — because implementation depends on people understanding what changed.

TRANSLATION → POLICY / PROCESS / SYSTEM → SOMETHING PEOPLE CAN USE
Pattern recognition
I keep ending up one step outside the box.
Usually because...
01
The process crosses more than one team.
02
The system technically works, but the experience does not.
03
The information exists, but people cannot find or understand it.
04
Someone is doing repetitive work that probably should not require a person.
05
Nobody quite owns the whole problem.
↳ which may explain why “useful in the in-between” feels more accurate than any single job title.
A note to future me

Keep following the weird bits.

The detours are where I picked up the ability to move between operations, systems and communication. They are not distractions from the career story. They are the career story.

PERMISSION SLIPIt is okay if the next interesting thing does not fit neatly under “HR” either.
Want the boring CV?

Or the less boring conversation about any of this.

ay@alphonseyu.com →