Growing Fast? Keep Things From Falling
One of the most common challenges we hear from growing organizations sounds something like this:
"We have a lot going on.” A project gets started but never finished. A task is discussed in a leadership meeting and nobody follows up. A new employee unknowingly begins solving a problem another department has already spent six months working on. Three people are researching the same vendor. Someone leaves the company and takes critical project knowledge with them (ooof). A year later, leadership realizes an important initiative stalled because everyone assumed someone else was handling it.
This isn't usually a people problem. It's a systems problem.
As organizations grow, information becomes fragmented across meetings, emails, Slack messages, spreadsheets, notebooks, project plans, and people's memories.
The role of an exceptional Executive Assistant is not simply to schedule meetings.
It is to create visibility, accountability, and continuity across the organization all for their leaders.
Here are six systems we recommend.
1. Create One Source of Truth
The biggest mistake growing companies make is allowing project information to live in multiple places.
Meeting notes are in Google Docs. Tasks are in Asana. Updates happen in Slack. Leadership decisions live in email.
Nobody knows where to look.
Choose one central operating system.
Options include:
Notion
ClickUp
Monday.com
Airtable
While many of these tools can work well, our team has increasingly found ourselves recommending Coda to growing organizations because it combines documents, databases, project management, meeting notes, dashboards, and automation into a single connected workspace.
Most tools force you to choose between a document and a database. Coda allows you to build both in the same place.
For example:
A leadership meeting agenda can automatically pull in open action items.
Action items can automatically roll into department project plans.
Project plans can roll up into quarterly goals and OKRs.
Executive dashboards can pull real-time information from all of the above.
Instead of maintaining separate spreadsheets, meeting notes, trackers, and project plans, everything lives within the same ecosystem and updates dynamically. This becomes especially powerful as organizations grow because information remains connected.
The tool matters less than the discipline.
Every major initiative should have:
Owner
Status
Priority
Due dates
Related documents
Key decisions
Next steps
When someone asks, "What's happening with that project?" there should be one answer and one place to look.
2. Build a Leadership Action Tracker
Most work dies after meetings. Not because people don't care, but because they leave with good intentions and immediately return to overflowing inboxes. Every leadership meeting should generate a living action tracker.
Each item should include:
Task
Owner
Date assigned
Due date
Current status
Last update
The tracker should be reviewed at the beginning of every leadership meeting before new topics are discussed.
Not annually. Not quarterly. Every single meeting. What gets reviewed gets completed.
3. Connect Meeting Agendas to Project Tracking
Most companies treat meetings and project management as separate systems, they shouldn't be. A strong EA creates a workflow where:
Projects generate agenda items.
Agenda discussions generate decisions.
Decisions generate tasks.
Tasks automatically flow back into project tracking.
For example:
A leadership team discusses a website redesign.
The discussion generates three action items.
Those action items automatically appear in the project tracker.
The project tracker updates the status.
The status appears in the next leadership agenda.
Nothing gets lost between conversations.
4. Implement Quarterly OKR Tracking
Many organizations have goals.
Far fewer have visibility into whether they're making progress. We recommend maintaining a simple Objectives and Key Results (OKR) dashboard.
For every major company objective:
What are we trying to accomplish?
How will we measure success?
Who owns it?
What is the current status?
The EA often becomes the steward of this process by collecting updates, identifying stalled initiatives, and surfacing risks before leadership meetings. The goal is not reporting. The goal is awareness.
5. Create Weekly Executive Updates
One of the most effective systems requires surprisingly little technology—and very little additional effort from leadership. A common mistake organizations make is creating reporting processes that become a second job for everyone involved.
The goal should never be to create more work. The goal should be to create more visibility.
In a well-designed system, project owners are already updating the status of their work within the organization's operating platform—whether that's Coda, Notion, Airtable, ClickUp, or another project management tool. The Executive Assistant's role is not to chase updates, maintain spreadsheets, or manually build reports every week.
Instead, the EA designs and maintains a dashboard that automatically surfaces the information leadership needs most.
For example:
Projects completed this week
Upcoming milestones
Overdue items
High-priority initiatives
Roadblocks requiring executive decisions
Projects lacking recent updates
Cross-departmental dependencies
Rather than asking executives to attend more meetings or read longer reports, the dashboard provides a simple, real-time snapshot of what matters most. The beauty of a connected system is that information only needs to be entered once. The project owner updates the project. The project updates the dashboard. The dashboard updates leadership. No duplicate work. Just visibility.
When implemented correctly, executives can quickly answer questions like:
What are our biggest risks right now?
Which projects are stalled?
Where do we need decisions?
What has changed since last week?
Who may need support?
Benefits include:
Reduced duplicate work
Better cross-functional visibility
Faster decision making
Earlier identification of roadblocks
Most importantly, everyone can see what everyone else is working on. This alone prevents countless duplicated efforts.
6. Build an Organizational Memory System
One of the greatest hidden risks in growing organizations is knowledge loss. Someone leaves. A team reorganizes. Priorities change. Six months later, leadership asks: "Didn't we already solve this?"
An organizational memory system captures:
Major decisions
Vendor evaluations
Project outcomes
Lessons learned
Strategic discussions
Historical context
The goal is simple: Never solve the same problem twice. Never pay for the same research twice. Never lose valuable institutional knowledge because one person left the company.
The Real Job of an Exceptional EA
The best Executive Assistants are not simply managing calendars. They are managing clarity. They connect conversations to action. They connect action to accountability. They connect accountability to results. As organizations grow, complexity is inevitable. Confusion doesn't have to be.
The right systems—and the right person maintaining them—ensure that important projects continue moving forward, critical information remains visible, and great ideas don't get lost in the noise of a growing business.