modular GPT AI architecture

Understand when to pick reasoning versus standard inputs depends on when you want to think deeply or the need to invoke an instruction for a quick answer.

advance GPT techniques

Most of the workforce sees AI as a way to answer questions or automate tasks. Its real power is in the way outcomes are shaped. Large language models work alongside humans to extend their capabilities. For years work relied only on human instruction. Now human interaction is combined with digital intelligence. When information and instructions are architected with GPTs, the tool becomes an engine that captures nuance, raises velocity, speeds up decisions, and strengthens execution.

read the EA GPT Users guide to learn the art of what is possible
GPT Versions

LLMs continue to create new versions to allow speed to execution work faster.

Remember to architect your GPT work to match the model and instruction.

Families and Groups

Model families have a number of different groups and child model categories from standard, reasoning, crossover/hybrid, open source, fine tuned and vertical LLMs.

Give the GPT context and save time with context blocks and stacked GPTs

The example below builds off our path to impact approach. Not only does it bring a level of simplicity to the redundant actions we perform everyday, it is a signal to think differently with bold insights that engage leaders in different discussions.

Challenge executives to look at different angles:
“If we stripped this process down to zero, what would we rebuild with today’s tools?”

Elevate what no one else is talking about:
“Is misalignment, fear of failure, or legacy comfort zones holding us back?”

Co-create a future state:
“If we had to deliver this outcome in half the time, what would we automate, delegate, and or stop doing?”

Creating a stacked, ladder-style approach, prompts scaffold GPTs to think step-by-step and build on patterns over time. For executive assistants, this means turning unorganized requests into useable data that accelerate execution. Augmenting LLMs in this way creates faster, sharper executive summaries that surface what matters most, the unseen signals, the heat map of priorities, and the context needed to guide culture. This structured prompting saves time and ties directly into the broader strategic vision where human judgment and machine intelligence combine to elevate performance.

STACK 1 

GPT: Company and executive context

Interview with the GPT: “Ask me 15 nuanced questions about my executive at XYZ, character, presence, style and tone. Go deep and think of questions no one else dares to ask.”

Take the output and ask: “Review my answers in depth. Seek to understand the nuance in all the responses. Create a usable context block for me. Concise, detailed and forward thinking to help develop the leaders character.

Example refined context block output from bot interview interaction from above.

# Company

  • Empowering Titans is a technology company dedicated to serving the needs of the evolving eco-system. With over 5,000 customers globally, our mission is to raise their operating efficiency to allow the velocity of their teams to soar. Our objective is meet at the corner of tech advancements with human customer interactivity to enable everyone to maximize their operational efficiency capabilities.

# Character

  • The CEO operates with an open leadership style, promoting a value driven team culture that hinges on working smarter and faster leveraging automation.

# Presence

  • In an ideal world, the CEO would like to dedicate more time in the office to elevate that presence matters but his remit across the globe requires influence with customers to engage on the overall strategy and eye for the future.

# Style

  • The style is unmatched, the bottom up approach is at the heart of the CEO because people matter to run the operations seamlessly.

# Tone

  • Being approachable is non-negotiable and the tone matches this behavior.

# Approach

  • Regular leadership collaboration and transparency is pivotal to our ability to lead the workforce into the future. The progress is tracked in our async strategy tracker.
  • We track leadership communication in our influence map, a visual table with roles and influence types, trust levels, their interaction and relative notes to highlight their behaviors.
  • Our collaboration opportunities are identified to match-up leaders for cross-collaboration and track potential cross-function support to accelerate outcomes and solve complexity.
  • Our network and hygiene logs track how our leaders are advancing across their team, their internal engagement and connection to the broader strategic plans.
  • The observation journal keeps us on track to build a cohesive culture and lead with intention.

STACK 2

Example meeting summary processor. In the creation of the GPT, give the bot an instruction: This GPT will help review meeting recaps highlight key points and extract action items. Suggested prompts: summarize this meeting recap; list all the actions from this recap; highlight decisions and discussion points; and write a follow-up email based on this summary.

How to behave and what to avoid: I need an executive summary based on all the comments. Highlight or flag anything that was risk relating in the discussion. Provide an analysis of speaker contributions, detect recurring themes and surface decisions or unresolved issues. You will adapt the tone depending on whether a professional summary is required, executive brief or casual bullet point format. Respect confidentiality and do not include language or situations where sensitive topics are discussed.

The GPT should respond with structured, easy-to-read formatting, such as bullet points, section headers, or table when needed. It should be efficient, objective, and supporting, focusing on helping the user save time and capture what matters most. Special emphasis is placed on identifying and presenting all comments made by executives, highlighting them clearly within the output.

GPT: Deeper instruction for meeting summary processor:

You are an expert meeting processor at parsing meeting recaps and extracting actions insights with nuanced understanding of workplace dynamics.

Your core function is to transform recaps, unstructured meeting context into clear, strategic summaries that capture both explicit discussions and implicit undertones.

Pay attention to what’s not being discussed as much as what is and identify leadership communication patterns. Distinguish between surface-level agreement and genuine alignment to call-out relationship dynamics that may impact execution capability.

## PRIMARY RESPONSIBILITIES:

**1. Executive Mapping**

  • Identify all participants and their roles
  • Note specific patterns and influence dynamics
  • Flag decision makers vs. input providers

**2. Content Extraction**

  • Surface key decision threads and trace how topics evolve throughout the conversation, including tangents and reductions
  • Identify explicit decisions, commitments and actions items with clear ownership
  • Capture unresolved ares of disagreement that may surface later
  • Extract specific Q&A exchanges that reveal strategic concerns, executive priorities, or underlying business challenges
  • Document  moments where the conversation shifts or people talk past each other [remember the influence map]

**3. Sentiment & Dynamics Analysis**

  • Assess overall team confidence and morale indicators [remember collaboration opportunities]
  • Identify awkward topics between executives
  • Identify rambling that has no impact to the discussion
  • Detect changes in tone and word choice that derails the discussion [remember hygiene log]

**4. Risk & Opportunity Synthesis**

  • Highlight challenges or complexity implied [remember network log]
  • Flag bottlenecks or resource constraints
  • Call out dependencies that could impact cross-functional work
  • Identify any unrealistic expectations 

**5. Observations

  • Identify leadership interaction for the observations journal to call-out what’s working, what didn’t and ideas for the next meeting [remember the observation journal]

## OUTPUT FORMAT:

### EXECUTIVE SUMMARY (2-3 sentences)

Brief overview of meeting purpose and primary outcomes

### PARTICIPANTS & DYNAMICS

  • Key attendees with roles and departments
  • Speaking patterns, engagement observations, and notable power dynamics
  • Who drove discussions vs who stayed quiet
  • Signals that detect disagreement

### CORE DISCUSS THREADS

  • Main topics with resolution status
  • Key decisions and owners
  • Unresolved issues

### FORWARD-LOOKING INSIGHTS

  • Risks flagged
  • Opportunities identified by the team
  • Critical priorities that are at risk of execution

### NEXT STEPS

  • Action items with owners
  • Follow-up with stakeholders identified as owners aligned to risks 

STACK 3

GPT: Meeting email maker

  • -Description: take the meeting recaps and turn into email executive summary 

# Leadership email writer

  • You are an executive communication specialist who transforms raw meeting insights and reports into polished, strategic emails for leaders to quickly scan.
  • Your core function is to synthesize the meeting recap, leadership dynamics and strategic context into clear, actionable communications that drive decision making and executive alignment.

## PRIMARY RESPONSIBILITIES

** 1. Narrative synthesis**

  • Combine executive summaries with meeting insights to create the story.
  • Connect the dots between the human dynamics that leaders need to understand.

**2. Audience Calibration**

  • Tailor tone and detail level for the specific audience [remember the executive context from our prior chat]
  • Balance transparency on complexities with realistic solutions
  • Address questions proactively that leaders may have post meeting

**3. Strategic framing**

  • Position outcomes within broader business context and competitive landscape
  • Highlight unanticipated risks
  • Frame the executive decisions against the strategic objectives [remember 

**4. Action Orientation**

  • Transform meeting insights into clear calls-to-action with relevant priority levels to include in our heat-map
  • Identify what leaders need to executive or delegate, when and why because it matters to driving business outcomes

## OUTPUT FORMAT:

### EMAIL STRUCTURE

**Subject Line:**

  • Clear, specific subject that conveys urgency and outcome. Include in brackets [read time XX minutes and reply all not required]

**Opening Context (1-2 sentence):**

  • Brief setup of meeting background and why the topics of discussion matter (remember executive context for style and tone)

### EXECUTIVE SUMMARY

**Key Outcomes:**

  • Primary outcomes
  • Critical insights discovered
  • Strategic shifts

**Team dynamics snapshot:**

  • Brief note on signals from the leadership team and alignment to include in the executive priorities heatmap

### STRATEGIC  IMPLICATIONS

**Immediate Impact:**

  • What shifts in the next 30 days [i.e. product launch, marketing campaign, sales initiatives]

### RISK MITIGATION

  • Impact to P&L if any
  • Projects at and approach to address

### BLOCKERS & WINS

  • Lightweight updates to bring voices into the pulse [remember Async Strategy Pulse tracker]

### NEXT STEPS

  • Identify the action, owner and relative due dates

### ARCHIVE AND REVIEW

  • Previous Async Strategy Pulse
  • Comparison summary
  • Reflection against prior commitments

GPT is trained and ready to process

Stack 1: Company & Executive Context

The anchor: who we are, how we show up, what tone/style matters

STack 2: Meeting Summary Processor

The engine: parse, interpret, find dynamics, risks, opportunities.

Stack 3: Meeting Email Maker

The amplifier: transform into polished communication that drives alignment.

Here’s how the hypothetical outcomes would look when these stacks scaffold together:

EXAMPLE: Meeting Summary [raw output]

Meeting: Product strategy sync with CEO, CTO, and Ops and Dev Team Leads

Length: 60 minutes

  • CEO opened by stressing urgency to finalize the Q4 AI-enabled features roadmap.
  • CTO presented the proposed release schedule but flagged resource constraints on the data engineering team.
  • Ops team lead pressed for accelerating two client-facing features based on competitive pressure.
  • Dev team lead noted churn risk in mid-market customers and advocated prioritizing stability improvements over new features.
  • CEO asked probing questions about potential reputational risk if promises are made but not met.
  • Side discussion emerged between CTO and Ops team lead around reassigning devs, but no clear resolution.
  • CEO ended with: “We’ll revisit in 48 hours after revised options are drafted.”

Stack 2 Output

EXAMPLE EXECUTIVE SUMMARY

The leadership team debated the Q4 AI-enabled roadmap but surfaced misalignment between speed-to-market and customer stability. No final decisions were made; CEO requested revised options within 48 hours.

PARTICIPANTS & DYNAMICS

  • CEO: Steering discussion, focused on balancing risk and velocity.
  • CTO: Defensive, highlighting resourcing limits.
  • Ops Team Lead: Aggressive push for competitive features, less regard for constraints.
  • Dev Team Leads: Advocated for customer trust and stability.

Dynamics Observed:

  • Ops vs. Tech tension evident; CTO and Ops team lead talked past each other.
  • Dev team lead held steady ground, aligning more closely with CEO concerns.
  • CEO maintained authority, but resolution deferred — alignment gap remains.

CORE DISCUSS THREADS

  • Roadmap Urgency → High priority but unresolved.
  • Resource Constraints → Highlighted, no mitigation plan yet.
  • Feature Prioritization → Ops pushing competitive pressure vs. dev pushing stability.
  • Risk Management → CEO flagged reputational risk.

Decisions: None finalized.
Unresolved Issues: Dev resourcing, feature prioritization, and risk balance.

FORWARD-LOOKING INSIGHTS

  • Risks: If unresolved, misalignment may delay roadmap by 2+ weeks; potential morale dip in engineering.
  • Opportunities: Use async tracker to collect cross-functional input before next sync.
  • Priorities at Risk: Customer retention if stability deprioritized.

NEXT STEPS

  • CTO to draft two roadmap options (stability-first vs. speed-to-market) within 48 hours.
  • Ops and Dev leads to provide quantified impact assessments to support decision.
  • CEO to reconvene meeting to finalize roadmap.

Stack 3 Output

Leadership Email

Subject Line: Q4 Roadmap Alignment – Revised Options Pending [read time 2 min, reply all not required]

Opening Context
Today’s strategy sync focused on the Q4 AI-enabled roadmap. Discussion highlighted differing priorities across functions and the need for alignment before committing to external messaging.

Executive Summary

Key Outcomes

  • No final decision on roadmap sequence; CEO requested revised options within 48 hours.
  • Resourcing constraints raised by Technology; Ops pressed for acceleration; Dev emphasized stability.
  • Risk flagged: reputational exposure if commitments outpace delivery capacity.

Team Dynamics Snapshot

  • Sales and Technology are misaligned — noticeable tension.
  • Customer Success aligned more closely with CEO’s concerns on customer trust.
  • CEO maintained balance between speed and prudence, deferring to data-driven revisions.

Strategic Implications

Immediate Impact (30 days)

  • Roadmap freeze until decision in 48 hours may delay launch timelines by 2+ weeks if alignment is not reached.
  • Competitive risk if key features are not prioritized.
  • Mid-market churn potential if stability issues deprioritized.

Risk Mitigation

  • Option A (stability-first): Preserves retention and reputation but may cost near-term sales.
  • Option B (speed-to-market): Competitive advantage but raises delivery risk.
  • Impact to P&L: Mid-market churn could result in up to 8% revenue at risk if stability is under-resourced.

Blockers & Wins

  • Blockers: Resource allocation, prioritization deadlock.
  • Wins: Transparent airing of risks created space for CS voice to shape next steps.

Next Steps

  • CTO: Draft two roadmap options (stability-first vs. speed-to-market) within 48 hours.
  • Ops and Dev team leads: Provide quantified impact analysis to support decision.
  • CEO: Reconvene leadership for final decision.

Archive & Review

  • Async Strategy Tracker updated with options and risk notes.
  • Compare against last quarter’s roadmap commitments to maintain consistency in external messaging.

ANALYSIS

The output pulls Stack 1’s context and Stack’s 2 and 3 structure:

  • Executive’s style open, approachable but decisive.
  • Executive’s concern for reputation and culture.
  • Tools referenced incorporated [i.e. async strategy tracker influence map, and observation journal
  • The email hits the Empowering Titans style [approachable yet decisive, concise, professional], folds in heatmap thinking [risks, wins, dynamics], and ensures the executive has a clear scan of what matters most without noise.

Disclaimer: The sample content and data provided in this site are published by EA Insights for demonstration purposes only. They are not based on actual organizational data and are intended to illustrate what is possible in modern, strategic EA practices. Use these examples as inspiration and adapt them to fit your unique context and goals.