Executive Support • Operations • Systems • Automation

Support that thinks
beyond the task.

I build the structure behind the work: clearer ownership, visible priorities, thoughtful executive support, documented processes and workflows that reduce unnecessary manual handoffs.

Explore the work →
Project tracking result↗
40%

Improvement in on-time project completion
through clearer ownership, deadlines and visibility.

Operating loop

CAPTURE → CLARIFY → ASSIGN → EXECUTE → CLOSE

01 • Systems & automation

The tools are the canvas. The thinking is the skill.

The portfolio recreates the architecture and decision-making behind systems I have built, without exposing previous employers' proprietary work.

01 • Notion delegation system

Executive Command Center

A recreated demonstration based on a Notion task-management system built using the Sam Corcos delegation approach. Ownership, priority and next actions become visible instead of living in memory or scattered messages.

EXECUTIVE COMMAND CENTERTODAY
25Tasks
8Waiting
12Active
5Due Today
TaskOwnerPriorityDueStatus
Review proposalVivianHIGHTodayWAITING
Board materialsVivianHIGHFriPREPARING
Vendor approvalOpsMEDThuIN PROGRESS
Client follow-upSalesLOWFriASSIGNED
DELEGATION FLOW
CAPTUREGet work out of memory.
CLARIFYDefine the outcome.
DELEGATEAssign ownership.
TRACKMake progress visible.
REVIEWSurface blockers.
CLOSEConfirm the result.
02 • Google Forms + Zapier + Monday.com

From intake to execution.

When a potential client submitted a form, the automation could route the request to the right workspace, create the work item, assign an owner and start the appropriate process.

WORKFLOW ARCHITECTUREROUTING
FORMApplication submitted.
ZAPIERTrigger fires.
ROUTECorrect workspace + process.
MONDAYItem populated.
OWNERAssigned automatically.
PROCESSVerification → completion.
ROUTING CAN BRANCH
WORKSPACE A
WORKSPACE B
WORKSPACE C
Why this matters: there were several workspaces and different forms, so the workflow had to start the right process, in the right place, with the right person assigned.
03 • Client onboarding

Inside the workflow.

A fictionalized Monday.com-style board showing how automated client intake can become visible operational work.

New1
Acme ConsultingApplication received
AUTO-CREATED
Verify1
BrightPath Ltd.Docs review
ASSIGNED
In Progress1
Summit PartnersOnboarding
OWNER: OPS
Waiting1
Verte SolutionsAwaiting info
FOLLOW-UP
Complete1
North GroupCompleted
CLOSED
04 • Project handover

Make the transfer clean.

A structured handover moves context from the outgoing owner to the next owner without relying on a long chain of messages.

OUTGOING OWNER
Context • files • open work • decisions
HANDOVER PACK
Dependencies • deadlines • next actions • risks
NEW OWNER
Briefed • assigned • ready to continue
02 • Executive support

Calendar management that looks like a real calendar.

The transformation is not “more organized tasks.” It is better use of time: conflicts resolved, meetings consolidated, preparation protected and focus blocks deliberately created.

Week of May 19–23, 2025Executive calendar • fictionalized demonstration
MON 196 meetings
TUE 205 meetings
WED 214 meetings
THU 225 meetings
FRI 234 meetings
8:00
Planning & prioritiesFocus block
Leadership prep
Deep workProtected time
Weekly review
9:00
Leadership meeting09:00–09:45
Client strategy09:00–10:30
Leadership sync09:00–09:45
Client call09:00–09:45
Board prep09:00–10:30
10:00
Team check-in10:00–10:45
Decision review10:00–10:45
Operations sync10:00–10:45
11:00
Client meeting11:00–12:30
Focus blockProtected time
Vendor call11:00–11:45
Client meeting11:00–11:45
Deep workProtected time
12:00
Lunch / buffer
Lunch / buffer
Lunch / buffer
13:00
Project review13:00–14:30
Team check-in13:00–13:45
Client call13:00–13:45
Project review13:00–14:30
Leadership sync13:00–13:45
14:00
Executive focusProtected time
Preparation blockMeeting prep
Executive focusProtected time
15:00
Stakeholder call15:00–15:45
Vendor review15:00–15:45
16:00
Buffer / follow-upProtected
Admin closeout16:00–16:45
Decision meeting16:00–16:45
Buffer / follow-upProtected
Weekly closeout16:00–17:30
MeetingsClient / priorityFocus / bufferFictionalized calendar demonstration
BEFORE • REACTIVE CALENDARNeeds redesign
MON 197 meetings
TUE 208 meetings
WED 216 meetings
THU 228 meetings
FRI 236 meetings
9:00
Leadership sync09:00–10:30
Client call09:00–10:30
Strategy meeting09:00–10:30
Operations09:00–10:30
Board prep09:00–10:30
10:00
Vendor call10:00–10:45
Team check-in10:00–10:45
Decision review10:00–10:45
Client call10:00–10:45
Internal sync10:00–10:45
11:00
Client meeting11:00–12:30
Project review11:00–12:30
Vendor review11:00–12:30
Client meeting11:00–12:30
Stakeholder call11:00–12:30
12:00
13:00
Project review13:00–14:30
Leadership13:00–14:30
Client call13:00–14:30
Project review13:00–14:30
Team sync13:00–14:30
14:00
Follow-up14:00–14:45
Admin14:00–14:45
Urgent call14:00–14:45
Internal14:00–14:45
Catch-up14:00–14:45
15:00
Stakeholder call15:00–16:30
Client call15:00–16:30
Decision meeting15:00–16:30
Vendor review15:00–16:30
Weekly review15:00–16:30
What the recruiter can see: stacked meetings, little breathing room, visible conflicts and almost no protected preparation or focus time.
AFTER • INTENTIONAL CALENDARRedesigned
MON 195 meetings
TUE 204 meetings
WED 214 meetings
THU 224 meetings
FRI 234 meetings
9:00
Planning + priorities09:00–10:30 • focus
Leadership prep09:00–09:45
Leadership sync09:00–09:45
Deep work09:00–10:30
Weekly review09:00–09:45
10:00
Leadership meeting10:00–10:45
Decision review10:00–10:45
11:00
Client meeting11:00–12:30
Focus block11:00–12:30
Vendor call11:00–11:45
Client meeting11:00–11:45
Deep work11:00–12:30
12:00
Lunch / buffer
Lunch / buffer
Lunch / buffer
13:00
Project review13:00–14:30
Team check-in13:00–13:45
Client call13:00–13:45
Project review13:00–14:30
Leadership sync13:00–13:45
14:00
Executive focus14:00–15:30
Preparation block14:00–15:30
Executive focus14:00–15:30
15:00
Stakeholder call15:00–15:45
Vendor review15:00–15:45
What changed: meetings were consolidated, conflicts removed, preparation protected and focus/buffer time deliberately created.
The principle

Calendar management is time design.

The job is not to make the calendar look full. It is to make the executive's time reflect the work that matters.

The test

Can the calendar tell the story?

If a leader has an important decision, project or client meeting, the calendar should show the preparation, buffers and follow-through around it, not just the meeting itself.

03 • Digital workspace organization

I organize digital clutter too.

A browser can become a second desk: dozens of tabs, half-finished research, work tools, reference pages and “I'll come back to this” links. I like turning that clutter into a workspace that makes sense at a glance.

Tracking
AI
Drive
Docs
Socials
Education
Remote work
workspace / organized tabs
Organized Browser WorkspaceFictionalized demonstration

Tracking & Work

Project tracker↗
Monday.com↗
Notion↗
Task dashboard↗

Research & AI

AI workspace↗
Research brief↗
Reference article↗
Saved resources↗

Documents

Google Drive↗
Working document↗
Client brief↗
Templates↗

Communication

Gmail↗
Slack↗
Socials↗

Learning

Course dashboard↗
Education resource↗
Notes↗

Reference / Later

Remote work guide↗
Saved reference↗
Ideas to revisit↗
The problemImportant pages get buried in a wall of open tabs. The result is visual noise, repeated searching and a higher mental load.
The resultTabs are grouped by purpose so the browser becomes a usable workspace: work, research, documents, communication, learning and reference.
A small thing that matters

Digital organization is executive support too.

Sometimes the productivity win is not another automation. It is making the information someone already uses easier to find, understand and return to.

My approach

Group by purpose, not by panic.

The goal is a workspace where the next click is obvious and “Where did I put that?” becomes a much rarer question.

03 • Recruitment operations

LinkedIn sourcing with a visible candidate pipeline.

A recreated operations dashboard showing how candidate sourcing, progression and follow-up can be made visible. Candidate names and data are fictional.

RECRUITMENT OPERATIONSFICTIONAL DATA
Outreach2
Alex JohnsonOperations Associate
LinkedIn
SOURCE
Bianca MillerExecutive Assistant
LinkedIn
CONTACT
Screening2
Carlos MartinezProject Coordinator
Referral
REVIEW
Diana WilsonCustomer Support
LinkedIn
SCREEN
Interview1
Ethan BrownAdmin Assistant
LinkedIn
SCHEDULE
Shortlisted1
Candidate FOperations Support
Referral
MANAGER REVIEW
Follow-up2
Candidate GExecutive Assistant
NEXT ACTION
Candidate HProject Coordinator
FOLLOW-UP
Workflow
LINKEDINSource relevant candidates.
CAPTURERecord candidate information.
SCREENReview and organize.
PIPELINETrack stage.
FOLLOW-UPKeep next action visible.
Why it matters

Recruitment becomes an operating process, not a pile of profiles.

The point is visibility: who is where, what happens next and what needs attention.

04 • Project tracking
40%
IMPROVEMENT IN ON-TIME PROJECT COMPLETION

The tracker was not the magic. Visibility was. Once work had a clear owner, deadline and status, it became easier to see what needed attention before the deadline became an emergency.

Before
After
05 • Process documentation

Process documentation people can actually use.

A recreated client onboarding SOP based on the type of process documentation I have built.

CLIENT ONBOARDINGSOP / DEMO
TRIGGERNew form submission
01Review required information
02Verify client details
03Create / confirm workflow item
04Assign process owner
05Begin onboarding
06 • Demo Lab

A portfolio-owned working demonstration.

A fictional client submits a form → the workflow routes the request → creates the task → assigns an owner → starts the process.

Try the workflow
01 • FORMApplication submitted.
02 • TRIGGERAutomation fires.
03 • ROUTECorrect workspace selected.
04 • CREATEWork item created.
05 • ASSIGNOwner attached.
06 • GENERATENext tasks created.
07 • STARTProcess begins.
Status: Waiting for submission.
07 • How I think

The operating system behind my work.

Five habits that shape how I support leaders and teams.

01 • SEE THE SYSTEM

I look beyond the immediate task and ask what process produced it.

02 • MAKE OWNERSHIP CLEAR

Good systems make it obvious who owns the next move.

03 • REDUCE MEMORY LOAD

If something must be remembered repeatedly, it probably needs a system.

04 • DOCUMENT FOR HANDOFF

A process is stronger when someone else can follow it.

05 • CLOSE THE LOOP

Completion means the outcome is confirmed, not just that a task changed status.