GTA hiring automation flow
Back to Work
PROCESS AUTOMATION, 0→1

Automating GTA Hiring85% Fewer Errors, 8+ Hours Saved Per Cycle

Graduate hiring at Georgia Tech ran on spreadsheets, email chains, and manual re-entry across 7 disconnected tools. I designed and built an automated pipeline using Power Automate, SharePoint, and DocuSign that eliminated data re-entry and gave faculty real-time visibility into application status.

RoleService Designer & Builder
OrgGeorgia Tech College of Design
TimelineAug – Dec 2025
TeamSolo: research, design, build
StackPower Automate, SharePoint, Forms, DocuSign
01Problem Discovery

Manual processes were causing 85% of hiring errors

The GTA hiring process touched 7 different tools: email, spreadsheets, Word documents, a shared drive, DocuSign, HR portals, and a homegrown tracking sheet. Administrative staff entered the same applicant data 4–5 times per hire. Each transfer introduced errors. Applications got lost. Faculty had no way to check status without emailing someone.

I was asked to redesign the process end-to-end, with one constraint: faculty still needed flexibility to make nuanced hiring decisions. Full automation wasn't the goal. Eliminating unnecessary manual work was.

"I used to spend half my week just copying data between systems and answering status emails. Now I actually have time to help faculty with the decisions that matter." · Administrative Coordinator

Research at a Glance

6
Contextual inquiry sessions
8
Stakeholder interviews
3
Weeks shadowing hiring cycle
23
Process steps mapped
The Problem

23 manual steps, 7 tools, zero visibility

With 20–30 GTA hires per semester, small inefficiencies compounded into major time loss. Administrative staff spent 8–12 hours per hiring cycle on data entry and status tracking. The challenge wasn't just technical: ownership was unclear, stakeholders had conflicting needs, and previous automation attempts had failed because they didn't account for edge cases.

23
Manual steps in original process
7
Different tools used
8-12h
Time per hiring cycle
Stakeholder Map
Stakeholder map: hiring decisions involved faculty, admin staff, HR, and department heads with different visibility needs
02Research

Contextual inquiry revealed the real workflow

I ran 6 contextual inquiry sessions with admin staff, watching the actual workflow instead of trusting how people described it. Then I interviewed 8 stakeholders across faculty and admin roles and shadowed a full 3-week hiring cycle.

Affinity Mapping
Affinity mapping: 6 themes emerged around data handling, status visibility, and approval bottlenecks

Key Insights

Insight 01

Data re-entry was the error source

The same information was entered manually 4–5 times across systems. Staff spent more time verifying data than entering it. Implication: The system must capture data once at the source and propagate it automatically.

Insight 02

No one could see status without asking

Faculty had no way to check where an application stood. This generated dozens of status-check emails per cycle, adding overhead for admin staff who were already stretched. Implication: Status must be visible to all stakeholders without requiring manual updates.

Insight 03

Approval bottlenecks were invisible

Applications sat in email inboxes waiting for approval. Without visibility, delays weren't surfaced until they became urgent. Implication: The system must surface pending approvals and escalate automatically after a threshold.

Admin Staff Persona
Primary persona: Administrative Coordinator managing 20+ hires per semester across multiple faculty

Empathy Mapping

Synthesized administrative staff perspectives into an empathy map, capturing what users say, think, do, and feel during the hiring cycle. The frustration quadrant revealed emotional burden that wasn't visible in process documentation.

Empathy map for administrative staff
Empathy map: capturing coordinator mental models during hiring workflow
03The Build

One pipeline, one data source, zero re-entry

I built the workflow on Power Automate, wired into SharePoint, Microsoft Forms, and DocuSign. Data enters once, through a structured form, then flows through approval, offer generation, and onboarding with no manual transfer along the way.

Validation at entry

Format checks and required fields catch errors at the source, not downstream. Directly addresses Insight 01: if data only enters once, it only needs to be correct once.

Real-time status dashboard

Faculty and admin staff see application status without email. Eliminates the status-check overhead identified in Insight 02.

Automated offer letters

When faculty approves an applicant, DocuSign generates and sends the offer letter automatically. No manual document creation.

Approval escalation

If an approval sits untouched for 48 hours, the system sends a reminder. After 72 hours, it escalates. Surfaces the hidden bottlenecks from Insight 03.

The Process

From 23 steps to automated flow

I mapped the existing workflow to find where data transferred between systems and where errors were introduced. The original process had 23 discrete steps with 7 different tools and at least 4 manual data transfers per applicant.

Flow Chart Mapping
Initial flow chart mapping: identifying every touchpoint and data transfer in the existing process
Old Process Flow
Original process: 23 steps across 7 tools with manual handoffs at each transition

The redesigned process consolidates everything into a single pipeline. Data enters once and flows through to onboarding without re-entry.

New Process Flow
Redesigned process: single data source with automated routing and approval tracking

Project Timeline

The project followed a structured timeline from discovery through deployment, with key milestones for research synthesis, prototype testing, and phased rollout.

Project timeline Gantt chart
Project timeline: 5-month engagement from research through deployment
The Storyboards

Aligning stakeholders on the pain

I used storyboards to get buy-in from faculty and department heads who hadn't seen the administrative side of hiring. Showing the coordinator's experience, copying data between windows, fielding status emails, chasing down approvals, made the problem concrete for decision-makers who only saw the final result.

Storyboard 1 Storyboard 2
Storyboard 3 Storyboard 4
Storyboard 5 Storyboard 6
Storyboard 7 Storyboard 8
Storyboard 9 Storyboard 10
Storyboard 11
Complete storyboard sequence: from application submission through onboarding

Story Arc

Mapped the emotional journey of administrative staff through the hiring cycle. The arc revealed peak frustration points at data transfer steps and approval bottlenecks, informing where automation would have the highest impact.

Story arc visualization
Story arc: emotional journey through the hiring process with pain points highlighted
The Outcome

Measured against the previous 3 semesters

The system launched for the Spring 2026 hiring cycle. Results were compared against error rates and time tracking from the previous three semesters.

85%
Reduction in data errors (based on correction requests)
8-12h
Saved per hiring cycle (self-reported)
0
Lost applications (vs. 2–3 per semester previously)

"I haven't had to send a single status-check email this cycle. I can just look." · Faculty member

Time Savings Comparison
Before/after comparison: time spent on key administrative tasks
The Reflection

What I learned