How to Audit and Upgrade Your EA Tech Stack

As Executive Assistants, most of us now work across more platforms, apps, and systems than we probably realise, which is exactly why more of you are starting to audit and upgrade your EA tech stack rather than simply adding more tools on top of existing workflows.

A normal day can involve moving between calendars, inboxes, Teams or Slack messages, travel platforms, project management systems, meeting notes, AI tools, shared documents, expense systems, scheduling apps, and whatever new software somebody in the business signed up for last month after seeing a LinkedIn post about it.

Then add in ChatGPT, Microsoft Copilot, Gemini, NotebookLM, AI meeting tools, and all the other AI products currently appearing inside the platforms we already use every day, and suddenly the way we work looks very different from even two or three years ago. It also means many of us are now trying to upgrade your EA tech stack while still managing the day-to-day demands of the role at the same time.

As EAs, we are often the people trying to hold all of this together.

We are usually the person who knows where the file is saved, which system your Executive prefers to use, which meeting notes actually matter, which tasks are still outstanding, and which platform somebody forgot to check before asking if we had “seen the update yet”.

The problem is that many teams adopt new tools without ever reviewing whether they overlap with existing systems or whether they are actually helping people work better. One department uses Asana. Another prefers Monday. Somebody else creates a Teams Planner board. Your Executive still sends action points by email. Before long, information is spread across five different places and everybody assumes the EA somehow knows where everything lives.

That is why taking the time to audit and upgrade your EA tech stack can be really useful.

This article will walk through how to review the tools you currently use, where overlap might exist, where AI tools are genuinely helping, and where your workflows may be creating more work than necessary as you upgrade your EA tech stack. We will also look at how your Executive’s habits and communication style form part of your wider tech stack, because the way information moves through the Executive office affects almost every part of the EA role.

This cheat sheet is packed with curated prompts designed to help you with ChatGPT.

This isn’t just another AI list; it’s a collection of prompts written by Assistants, for Assistants, to help you get the most out of ChatGPT and start making a real difference in your day-to-day.

    What Is Your Tech Stack as an EA?

    When people talk about a tech stack, it can sound like something that only applies to IT teams or software companies, but as EAs, most of us already manage a tech stack every single day, whether we think of it that way or not.

    Your tech stack is the collection of tools, systems, platforms, and workflows you rely on to support your Executive, manage information, communicate with stakeholders, and keep work moving across the business.

    For most EAs, that usually includes calendar tools, scheduling software, communication platforms, travel systems, project management tools, shared documents, note-taking apps, file storage systems, expense platforms, and, increasingly, AI tools.

    You might be using Microsoft Outlook alongside Teams and Copilot. You may also have Slack open all day while managing projects through Asana, Monday, ClickUp, Trello, or Planner. Then there are travel platforms, password managers, expense systems, shared drives, OneNote, Google Drive, SharePoint, AI meeting assistants, and the running collection of browser tabs we all promise ourselves we will close later.

    AI tools are also becoming part of the normal EA workflow now.

    Many Assistants are experimenting with ChatGPT for drafting and research, Microsoft Copilot for meeting summaries and document support, Gemini inside Google Workspace, NotebookLM for organising information, and AI meeting tools that can record discussions, create summaries, and pull together action points.

    The interesting part is that many of these tools overlap.

    You can now create meeting summaries in Teams, Zoom, Copilot, Gemini, Fireflies, Otter, and other AI meeting platforms. You can manage tasks inside email platforms, project management systems, chat tools, and shared documents. Sometimes the issue comes from having too many tools trying to handle the same tasks at the same time. One team updates actions in Planner, another uses Asana, your Executive forwards tasks by email, and meeting notes are also in Teams. That usually means information gets duplicated or updates get missed, and the EAs end up spending extra time checking multiple systems to make sure nothing has fallen through the cracks.

    That is why it helps to think about your tech stack as more than software.

    Your tech stack also includes the way work actually flows through your Executive office.

    For example:

    • Where do meeting actions live after a call?
    • How are priorities communicated?
    • Where are briefing documents stored?
    • How does your Executive prefer to receive information
    • Which systems are people actually using consistently?
    • What happens when somebody is off sick or on annual leave?

    As EAs, we are often the people updating the systems, checking the information is accurate, chasing missing actions, preparing briefings from multiple sources, and making sure your Executive has the right information in the right place at the right time.

    We often move information between platforms, translate updates across teams, organise workflows, and ensure nothing gets lost between meetings, inboxes, chats, and project systems. That means we usually have a very clear view of which tools genuinely help people work better and which ones create extra admin without anybody fully noticing.

    Why EAs Should Audit Their Tech Stack

    For most EAs, a tech stack audit is really about making day-to-day work easier to manage and finding practical ways to upgrade your EA tech stack without creating even more admin.

    One of the biggest benefits when you upgrade your EA tech stack is saving time in your daily work and tasks. 

    That might mean that when you audit your tech stack, you’ll notice you begin to reduce manual admin, cut down on duplicated tasks, prepare for meetings faster, or simply find information quickly without checking five different platforms first.

    It can also help reduce duplication across the business.

    Many teams now have multiple tools doing very similar jobs. Tasks are copied between systems, and updates are repeated across email, chat platforms, and project tools. And you know that everyone is saving documents in different locations. EAs often end up spending extra time manually reconnecting information that should already be linked together.

    A stronger tech stack also affects the quality of support your Executive receives.

    When systems are clearer, and workflows are more organised, preparing briefings, tracking priorities, following up on actions, and keeping visibility over what actually needs attention all become much more manageable, which also means your Executive spends less time searching for information or asking for updates, and you spend less time piecing everything together manually.

    As EAs, we usually notice very quickly when systems are helping work move smoothly and when they are slowing everybody down, which is why taking the time to upgrade your EA tech stack can have such a noticeable impact on the way you work every day.

    How to Audit and Upgrade Your EA Tech Stack

    If you want to upgrade your EA tech stack, the first step is usually to take a proper look at what you already use.

    As we’ve said, most of us add tools gradually over time and before long, you can end up working across dozens of systems without ever stopping to ask whether they are all still useful.

    That is why it helps to approach this as a step-by-step process rather than trying to completely rebuild everything at once.

    Step 1. List Every Tool You Use During the Week

    If you are trying to upgrade your EA tech stack, start by writing down every platform, app, and system you use in a typical week.

    Most EAs underestimate how many tools they actually use until they physically list them.

    That usually includes:

    • Calendars
    • Scheduling apps
    • Internal chat tools
    • Video meeting platforms
    • AI meeting note tools
    • Task management systems
    • Travel tools
    • Password managers
    • Reporting dashboards
    • Shared drives and file storage systems
    • AI Assistants like ChatGPT, Copilot, Gemini, and NotebookLM

    You may also notice that there are systems you use only because one particular stakeholder prefers them, even though the rest of the organisation works somewhere else. And you will also have your internal software tools, unique to your organisation. 

    Step 2. Work Out Which Tools You Actually Use Every Day

    Once you have the full list, separate the tools you genuinely rely on from those you occasionally open because someone else uses them.

    Ask yourself:

    1. Which tools save me the most time?
    2. Which tools create extra admin?
    3. Which systems overlap?
    4. Which subscriptions are barely being used?
    5. Which platforms do I avoid because they are difficult to use
    6. Which systems create duplicate work?

    This part matters when you upgrade your EA tech stack because many organisations now have multiple tools doing almost identical jobs.

    One team manages tasks in Planner. Another uses Asana. Somebody else prefers Monday. Your Executive forwards actions by email. Meeting summaries are sitting in Teams. Then somebody uploads the same update into Slack as well.

    That creates extra admin very quickly for EAs because, as we all know, we feel like we have to be across all the details, and quite often colleagues will come to us to ask us for things that they would find themselves if they were keeping up with all the communications on all of the different channels. 

    Step 3. Map Out How Work Actually Flows

    This is probably the most useful part of the process. Instead of focusing only on software, also start mapping how work actually moves through your Executive office.

    For example:

    • Where do meeting actions live after a call?
    • How are priorities communicated?
    • Where are briefing documents stored?
    • How do people request support?
    • Which systems does your Executive actually check?
    • Where do tasks get lost?
    • What happens when you are on annual leave?

    As we have already touched on earlier in the article, EAs are often the ones updating systems, chasing actions, preparing briefings, and ensuring information stays consistent across different platforms, which is usually why we spot workflow problems much earlier than everybody else.

    If you want to properly upgrade your EA tech stack, this step matters because the issue is often less about software and more about disconnected ways of working.

    I’m sure we’ve all seen it, teams often develop different ways of working without anybody properly reviewing whether the process still makes sense. Documents end up saved across multiple locations, updates are repeated across email and chat platforms, meeting recordings are created but rarely reviewed afterwards, and tasks slowly drift into our inboxes instead of sitting in one agreed system.

    All of this back-and-forth creates delays, duplicated work, and confusion about where information actually lives. Reviewing all workflows, along with the technology that supports them, will add a ton of value to your team and organisation. 

    Youtube video

    Step 4. Look at Your Executive’s Habits

    Your Executive’s workflow forms part of your tech stack too.

    That includes how they consume information, where communication gets stuck, how they manage meetings, and whether they rely too heavily on email for everything.

    Some Executives love collaborative documents. Others still ask for PDFs attached to long email chains. Some prefer Teams messages. Others forget to check anything outside their inbox.

    If you want to upgrade your EA tech stack, it helps to look at how your Executive naturally works rather than forcing another tool into the process.

    For example, there is very little value in introducing a new project management system if nobody updates it consistently or if your Executive still asks for updates through email anyway.

    The goal is to improve how information flows through the Executive Office, so work becomes easier to manage for everybody involved.

    Step 5. Identify What Is Creating Extra Work

    Once you have mapped your systems and workflows, warning signs and bottlenecks usually become much easier to spot. You may notice:

    • Your inbox acts as your task manager
    • Information is duplicated across platforms
    • Nobody knows where files are stored
    • People use three communication channels for one decision
    • Systems only work because you personally remember everything
    • You manually update multiple platforms with the same information
    • Your Executive struggles to find documents or actions •
    • Teams are paying for tools that nobody has been properly trained to use

    And I’m sure this all sounds very familiar, because as EAs we adapt to inefficient systems so gradually that we stop noticing how much extra work they create.

    We end up building workarounds.

    We remember where everything lives, and we manually reconnect information between systems because it feels quicker than fixing the actual workflow.

    But when you upgrade your EA tech stack properly, a lot of that unnecessary admin becomes much easier to reduce.

    Step 6. Decide Which AI Tools Are Actually Useful

    AI tools are now becoming part of most EA workflows, but that does not mean every tool deserves a place in your day.

    If you want to upgrade your EA tech stack, spend some time looking at where AI genuinely helps and where it may actually create more checking and editing work. Many EAs are currently experimenting with:

    • ChatGPT
    • Claude
    • Microsoft Copilot
    • Google Gemini
    • Google NotebookLM
    • AI meeting assistants like Fireflies, Fathom or Granola
    • AI search tools like Perplexity
    • AI scheduling tools like Vimcal EA or Motion

    Some of these tools are genuinely useful for drafting documents, summarising meetings, organising information, preparing first drafts, and speeding up repetitive admin tasks.

    But there are also areas where human oversight still matters a lot.

    AI can miss context. It can misunderstand priorities. It can produce incorrect summaries or create actions that were never actually agreed in a meeting. There are also confidentiality concerns depending on the type of information being uploaded into different platforms.

    That is why many EAs are finding the best results come from using AI to support first drafts, summaries, and information gathering, while still keeping people involved in decision-making, communication, and relationship management.

    When you upgrade your EA tech stack, AI should support the way you work rather than adding another layer of systems to manage.

    Step 7. Keep Reviewing Your Systems

    The next step is sometimes the hardest: actually making time to review your systems regularly rather than waiting until something breaks.

    One simple approach is to schedule a yearly review to upgrade your EA tech stack and assess what is still working well, which tools are no longer useful, where duplicate work is happening, and whether your workflows still make sense for how your Executive and wider team now operate.

    Even small adjustments can make a noticeable difference over the course of a year.

    When you upgrade your EA tech stack and take the time to properly review your workflows, you also start building a much clearer understanding of how teams communicate, where information gets stuck, which systems waste time, and where processes could work better.

    Tech awareness also improves visibility.

    The EAs who understand systems, workflows, AI tools, and operational gaps are often the people included in wider conversations around planning, efficiency, communication, and organisational improvements because they already have a practical understanding of how the business actually operates day to day.

    As EAs, we are often the people working across multiple departments, systems, meetings, and communication channels every single day, which means we usually spot operational problems much earlier than leadership teams who are further removed from the detail.

    Strong systems knowledge also supports long-term career development.

    The more you understand workflows, information management, AI tools, communication habits, and operational processes, the easier it becomes to contribute beyond traditional administrative support and become more involved in decision-making, project work, operations, and strategic planning.

    And in many organisations, modern EAs now have one of the clearest views of how information actually moves through the business, where work flows well, where people duplicate effort, and where systems are slowing everybody down.

    Share this article:

    Facebook
    LinkedIn
    Threads
    X
    Email
    Picture of Nicky Christmas

    Nicky Christmas

    I'm Nicky, the Founder and CEO of The EA Campus. Let’s continue the conversation over in our communities.

    The EA Campus Newsletter

    Join 30,000+ Assistants receiving our carefully crafted weekly newsletter packed with valuable tips, tricks, and insights tailored specifically for Assistants like you.