Mike WinklerAdvisory

What I have built

If I say I build HR AI workflows, you should be able to inspect the work.

For each project, I kept the starting problem, the tests, the failure, and the point where the tool has to stop. If it is a prototype, I call it one.

Working prototype

01

HR Mission Control

A prototype that watches a defined set of public sources, collects the relevant details, gives the work an owner, and keeps the decision and follow-through together.

HR Mission Control prototype showing public compliance items beside a decision packet with source provenance and visible information gaps
Private HRMC prototype · public-source test material · the yellow cards are gaps, not completion badges
  1. Update
  2. Summary
  3. HR review
  4. Owner
  5. Action
  6. Done

What I checked

  • 64 of 64 repeatable checks passed on July 15, 2026
  • 10 of 10 known items found in a small, human-checked source test on July 13, 2026
  • 240 local requests completed without a failure in a five-minute test on July 10, 2026

What it does not do

It helps organize the work. It does not give legal advice, promise complete coverage, or make policy decisions.

Read the full case study Read the public build notes

Designed workflow

02

Policy questions with sources

A design for the policy question that arrives with half the context missing. It answers from approved material, shows the source, and sends sensitive questions to the right person.

  1. Question
  2. Find
  3. Compare
  4. Show source
  5. Ask for help
  6. Save

What the design requires

  • Uses only the material the team approves
  • Shows the source and what is still unclear
  • Stops and asks for the right person on sensitive topics

What it does not do

It does not decide accommodations, leave, investigations, discipline, pay, immigration, or other sensitive employee matters.

Read the public build notes

Documented workflow

03

HRBP weekly brief

A way to turn the notes collecting across meetings, messages, and memory into one weekly brief an HRBP can actually use.

  1. Notes
  2. Facts
  3. Questions
  4. Owner
  5. Review
  6. Next step

What the design requires

  • Keeps facts separate from interpretation
  • Shows missing context instead of hiding it
  • Records who owns the decision and the follow-through

What it does not do

The workflow organizes the briefing. The HRBP still owns the relationship, the judgment, and every employee decision.

Read the public build notes

Start with a conversation

Tell me what is getting in the way.

Bring the workflow that keeps reopening, the approval nobody can reconstruct, or the pilot that looked better in the demo. We will start there. No deck required.

Book a conversation Or email mike@mikewinkleradvisory.com