Shiftbridge. The HR AI roadmap that picked decision-assist over autonomy.
Eight widgets. Each does one job. None of them tap send.
Late 2022, three weeks after ChatGPT shipped. Shiftbridge’s executive team had assembled a brief titled “Generation 4: HR with AI Agents.” The third bullet on page two read: “Design a conversational interface that lets managers do anything via chat.” The pressure was real, the timeline was real, the question underneath wasn’t yet articulated: what kind of AI does an HR product actually owe its users?
Designed canvas (Figma-style frame) titled “Shiftbridge AI, Decision-Assist Canvas.” Eight modular widgets in a 2×4 grid: Flight-Risk Signals, Pickup Warnings, Onboarding Drafts, 1:1 Prep, Manager Prompts, Performance-Conversation Drafts, Policy & Award Q&A, Compliance Reminders. Each widget shows a generated artefact and a “Review and Send” button.
The brief
Late 2022, three weeks after ChatGPT shipped. Shiftbridge’s executive team had assembled a brief titled “Generation 4: HR with AI Agents.” The document was confident: vision prose up front, four use-case clusters, a target reveal at their annual customer event eleven months out. The third bullet on page two read: “Design a conversational interface that lets managers do anything via chat.” The brief’s authors had spent the prior month watching the demos every other HR-tech platform was suddenly running. The pressure was real, the timeline was real, the question underneath wasn’t yet articulated: what kind of AI does an HR product actually owe its users?
The audit
The first three weeks we didn’t open Figma. We sat with twenty-two managers, HR generalists in mid-sized firms, people-and-culture leaders in early-stage startups, venue managers running fifteen-person teams in hospitality. We watched their week. The agentic-HR demos that year were impressive; they were also, almost without exception, designed by people who had never sent a written warning. The chronic pain wasn’t writing the warning, that’s the obvious generative-AI use case. The pain was noticing. Noticing that someone hadn’t been mentioned in a retrospective for two months. Noticing that a 1:1 commitment had fallen off the calendar three weeks ago. Noticing the engagement signal that drops six months before the resignation lands. The brief asked for a chat interface. The audit said: chat is a tell. Operators wanted help at specific moments, with specific work, surfaced before they thought to ask.
Sorting taxonomy. 30 candidate AI use cases assembled from the brief, vendor demos, and operator interviews, sorted into three columns: “Demo-magic (operators didn’t ask),” “Chronic operator pain (high-pull),” and “Wait, needs better data.” Eight cases in the middle column highlighted.
The work
We designed a canvas of eight modular widgets, each doing one job. Flight-Risk Signals surfaces tenure and engagement-pattern shifts months before a resignation lands. Pickup Warnings flags the slipped probation review, the missed 1:1 cycle, the lapsed development plan. Onboarding Drafts generates role-specific onboarding plans from JD plus team context. 1:1 Prep surfaces last-meeting commitments, recurring themes, and current project signals. Manager Prompts nudges the un-noticed. Performance-Conversation Drafts pulls threads from 1:1 notes, peer feedback, and project artefacts into a starting point, not a finished review. Policy & Award Q&A answers natural-language questions over the handbook and the Modern Awards. Compliance Reminders loops on visa renewals, casual-conversion timings, and penalty-rate windows.
The unifying principle: every widget assists the decision and produces an artefact the manager edits and signs. The Shiftbridge AI never taps send.
What we deliberately did not build
Two things were deliberately not built. The first was a chat interface as the primary surface, chat trades discoverability for power, and most managers don’t know what to ask. The second was autonomous action by any widget. HR is a domain where the wrong AI action has legal consequences, Fair Work, discrimination law, the procedural requirements around performance management. Decision-assist scales. Autonomous action exposes. We named both rejections in the executive handover, because the CTO needed to defend “we’re not building the autonomous agent” to a board that had been pitched the opposite for a year.
“We came in asking for a chat. You sent us out with a canvas. The discipline of choosing what the AI doesn’t do became the most important conversation we had that year.”
, Priya Anand, VP Product, Shiftbridge
The result
Twenty-four months on, six of the eight widgets had shipped in some form across the Shiftbridge platform. The two that hadn’t were the two we’d already flagged as needing better input data before they’d earn their keep, the product team validated that deferral independently. “Decision-assist over autonomy” became Shiftbridge’s stated AI principle, repeated in roadmap defences through 2024 when the broader market briefly fell in love with autonomous agents and then, in several high-profile cases, fell back out.
We’d attribute part of these outcomes to the canvas and part to honest confounds. Shiftbridge’s product team made hundreds of decisions over twenty-four months, the canvas was an input, not the only one. And the broader industry’s reckoning with autonomous-AI failures through 2024 made decision-assist a defensible default in ways the original audit could not have anticipated. The principle held up. Whether it would have held up without the broader market shift is the harder question, and one we’d rather name than pretend we’d already answered.
Closing
The takeaway: when the technology shifts under you, don’t optimise the obvious move first. Audit which work your users want help doing, and which work they want to keep doing themselves. AI maximalism isn’t a strategy. Choosing what the AI doesn’t do, and saying it out loud, is.