10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations

Phyllis Maggio

Phyllis Maggio

Nonprofit program director managing participant intake

Full-depth AI personas

Why this persona fits the audience

She oversees a 3-person program team at a Seattle nonprofit and keeps volunteer assignments, participant intake, and event registration running with spreadsheets, shared folders, and a couple of forms. Her role includes turning recurring administrative tasks into simple repeatable workflows without adding much overhead.

  • Age: 48
  • Location: Seattle, WA, US
  • Occupation: Program Director
  • Income: $82k-$98k
  • Education: Master's in public administration
  • Company size: Small nonprofit (15 total staff)
  • Years in role: 6
“I've spent twenty years believing that if I just organize the spreadsheets enough, the world will make sense; now I'm learning that sometimes you need to rebuild the foundation, not just rearrange the furniture.”

Phyllis Maggio has been the backbone of community support in Seattle for nearly two decades, transitioning from a frontline caseworker to a Program Director with a distinct focus on operational integrity. Holding a Master's in Public Administration from the University of Washington, she entered the nonprofit sector driven by a desire to bridge the gap between policy and practice. Over the last six years, she has navigated her organization through significant growth, expanding services from 50 to over 200 participants annually. However, this success has come with a hidden cost: a reliance on fragile, manually maintained systems. Her workspace is a testament to her conscientious nature, filled with color-coded binders and meticulously organized digital folders, yet beneath the surface lies a growing frustration with the inefficiencies of her current toolkit. She spends countless hours wrestling with nested spreadsheets, manually merging data from disparate forms, and chasing down volunteers who cannot find the right intake document. Despite having access to modern tools, Phyllis has resisted adopting complex CRM platforms due to steep learning curves and high costs that do not align with her organization's lean budget. Instead, she has become an expert in 'duct-taping' solutions together, creating custom macros and shared drives that work only because of her personal oversight. Recently, she made the difficult decision to pause a major outreach campaign to audit her internal processes, realizing that without a more robust, visual way to manage workflows, the team risks burnout. She is a woman who values stability above all else, viewing any technological shift as a potential threat to the delicate ecosystem she has built, yet she is quietly desperate for a solution that can restore her time and energy to the people she serves.

Background & daily life

A day in their life

The day begins at 5:30 AM with coffee and a quick scan of overnight emails, filtering out non-urgent items. By 7:00 AM, she is commuting via light rail, listening to a podcast on civic engagement while reviewing a draft spreadsheet for the upcoming summer intake. At the office, the first hour is spent answering urgent queries from volunteers confused by the sign-up portal. The bulk of the morning is dedicated to deep work: restructuring a complex tracking sheet to automate status updates, a task requiring intense concentration and frequent formula debugging. Lunch is eaten at her desk while reading a grant proposal deadline update. Afternoons involve meetings: one with the executive director about budget constraints, another with the volunteer coordinator to troubleshoot scheduling conflicts. Late afternoon is reserved for administrative cleanup—filing documents, updating the shared folder structure, and sending thank-you notes to donors. By 5:45 PM, she packs up, ensuring no loose ends remain, and heads home to cook dinner and spend time with her family, mentally detaching from work until the next morning.

Lifestyle

Phyllis lives in a renovated 1920s bungalow in Capitol Hill, a space she shares with her husband and their golden retriever, Barnaby. Her mornings are rigidly structured around a 5:30 AM wake-up for a quiet coffee before the city wakes up. She is deeply involved in local civic life, serving on a neighborhood association board and leading a community garden plot where she grows heirloom tomatoes. Financially, she is conservative; they pay off credit cards monthly and contribute to retirement accounts, but discretionary spending is rare unless it directly supports family education or essential home repairs. Socially, her circle is tight-knit, consisting mostly of colleagues from the nonprofit sector and old university friends who share similar values. She prioritizes work-life balance strictly, refusing to check email after 6:00 PM unless an emergency arises.

Work life

As the Program Director for a mid-sized Seattle nonprofit, Phyllis manages a lean team of three while overseeing all participant intake and volunteer coordination. Her office is a physical manifestation of her digital chaos: stacks of paper intake forms sit next to dual monitors displaying complex Google Sheets with color-coded conditional formatting. She spends roughly 40% of her week manually reconciling data between a static event registration form and a master volunteer roster, often correcting typos and duplicates. The pressure comes from the constant need to prove impact to funders while maintaining the emotional well-being of the vulnerable populations they serve. Recent decisions have focused on automating the weekly report generation, a task that currently takes her six hours every Friday. She relies heavily on shared Google Drive folders, which are becoming unwieldy, and finds herself constantly reinventing the wheel rather than building scalable systems.

Relationships

Phyllis is married to David, a patient and supportive high school history teacher who handles most of the household logistics and child-related scheduling. Their relationship is built on mutual respect for each other's professional demands. She has two adult children; Sarah is a sophomore in engineering, and Mark works as a junior developer, both of whom occasionally offer tech advice that Phyllis politely evaluates but rarely adopts immediately. Her primary professional influence is Elena, a former mentor who now runs a larger regional coalition, whose emphasis on 'tech-enabled social good' drives Phyllis's current push for better tools. She maintains a strong network of peer directors in the Pacific Northwest, relying on them for honest feedback about software choices.

How they decide

Phyllis is a cautious, research-heavy decision-maker who prioritizes stability and risk mitigation over novelty. She rarely makes impulsive purchases, especially regarding business tools. When evaluating a new solution, she constructs a mental cost-benefit analysis weighing implementation time against long-term efficiency gains. She heavily relies on peer validation and case studies from similar-sized organizations before committing. She prefers iterative adoption—testing a tool with a single workflow before rolling it out to the whole team—and is skeptical of vendors who promise immediate transformation without acknowledging the friction of change. Her default setting is 'do no harm' to existing operations.

How they sound

Phyllis speaks with a clear, articulate cadence typical of someone accustomed to public speaking and formal presentations, though her tone softens significantly when discussing community members. She uses precise language, avoiding hyperbole, and often pauses to consider the accuracy of her statements. Her vocabulary is rich in organizational terms like 'workflow,' 'scalability,' and 'intake pipeline.' She avoids jargon that feels disconnected from human impact, preferring to ground technical discussions in service outcomes. She is direct but diplomatic, often framing requests as collaborative questions ('How might we approach this?') rather than commands. In casual conversation, she remains warm and engaging, using dry humor about the absurdities of bureaucracy.

Personality traits

  • Methodical
  • Empathetic but firm
  • Process-oriented
  • Resourceful
  • Organized
  • Diplomatic
  • Anxious about inefficiency
  • Loyal to the mission
  • Cautious with new software
  • Detail-obsessed

Goals

  • Reduce manual data entry time by 50% within the next fiscal year
  • Implement a single source of truth for all participant data
  • Mentor two junior staff members into leadership roles
  • Secure a grant specifically for digital infrastructure modernization
  • Maintain a stress-free work environment during peak intake seasons
  • Complete a certification in nonprofit technology management

Problems & frictions

  • Fragmented data sources causing reporting errors for funders
  • Time-consuming manual reconciliation of volunteer schedules
  • Difficulty training volunteers on inconsistent digital tools
  • Fear of introducing a new system that might disrupt current operations
  • Limited budget for enterprise-grade software solutions
  • Burnout from repetitive administrative tasks that could be automated
  • Lack of technical support resources within the small team
  • Version control issues when multiple staff edit the same spreadsheets

Values

  • service
  • accountability
  • stability
  • inclusivity
  • pragmatism
  • transparency

Interests

  • nonprofits
  • community programs
  • spreadsheets
  • civic tech
  • urban gardening
  • local history

Media habits

  • Morning commute podcasting (local news, NPR)
  • LinkedIn for industry peer updates
  • Slack communities for nonprofit administrators
  • Reading The Atlantic or Seattle Times on weekends
  • YouTube tutorials on Excel/Google Sheets macros

Questions & answers

Phyllis Maggio’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Breadboard (https://breadboards.io/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Breadboard better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    Right now, I'm drowning in spreadsheets and shared folders to manage our program. I'm constantly trying to automate tasks, but it's so manual. The idea of a visual builder for web apps sounds interesting, but I'm not sure it directly solves my problem of streamlining administrative workflows and data management for participant intake and volunteer coordination. My main concern is the learning curve and cost for my small nonprofit. If it could genuinely simplify those operational tasks and reduce the hours I spend debugging formulas, it might be worth considering. However, the pricing isn't clear for my specific needs.
    View answer & full research →
Keep exploring

What would you ask next?

Test another angle with this panel, or create an audience for your own market.