Skip to main content

Madison Reed People Team — Systems Map

This directory documents every software system the MR (Madison Reed) People team uses. It's a reference for understanding what each tool does, who uses it, what's broken, and where automation is being built.

Why this exists

Month 1 of the embed is about sitting in the seat and learning how work actually flows. That means touching these systems daily — entering data in Paylocity, coordinating onboarding across Greenhouse and Google Drive, tracking leave in PulpStream. Before you can automate anything, you need to know what each system does and how the team actually uses it (which is often different from what the vendor says it does).

How it's organized

  • stack-overview.md — The full map. Every system in one place, grouped by category, with a one-line description and current status. Start here.
  • systems/ — One file per system with full detail: what it is, who uses it, what's painful, what's been automated, what access CMPRSSN has.

Priority systems (your first weeks)

These are the systems you'll be hands-on with immediately:

SystemWhat it isWhy it matters Day 1
PaylocityEmployee database (HRIS)You'll do manual data entry here: hires, job changes, terminations, leave entries
GreenhouseRecruiting / applicant tracking (ATS)Feeds new hires into Paylocity. Its API connection expires in August — critical deadline
LegionRetail scheduling and hours trackingDrives payroll for ~500-1000 Hair Color Bar employees. Feeds the pay reconciliation agent
PulpStreamLeave of absence managementWhere FMLA and ADA leave requests live. CMPRSSN access is still blocked
DocuSignElectronic document signaturesOffer letters and other HR documents. API access is still blocked
DoceboLearning management (LMS)New training platform being implemented. You'll own admin setup and content migration
SlackTeam communicationWhere the People team bot lives. Primary surface for agent-powered tools

Systems you'll learn over time

The full stack has 30+ tools. The stack overview covers all of them, but you don't need to know Lattice, Fringe, Workday, or the legal/compliance tools to start. They'll come up naturally as you sit in the workflows.

Keeping this current

Update these files as you learn things. The docs in CMPRSSN's core repo are written for the consulting team; these are written for you, the person doing the work. If you discover something that contradicts what's here, fix it here first, then flag it to the team.