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

Olive Koss

Olive Koss

Business systems manager at a mid-sized logistics company

Full-depth AI personas

Why this persona fits the audience

She runs a 4-person business systems team that maintains intake forms, dispatch workflows, and exception-tracking apps for operations and customer service. Her group uses a mix of spreadsheets, SQL views, and a few in-house web tools to support users across two US warehouses and a remote support desk.

  • Age: 41
  • Location: Columbus, Ohio, USA
  • Occupation: Business Systems Manager
  • Income: USD 112k base salary
  • Education: Bachelor's in Information Systems
  • Company size: Approximately 700 employees across multiple locations
  • Years in role: 6
“If it’s not documented, it didn’t happen, and if it’s not efficient, it’s costing us.”

Olive Koss has spent the better part of two decades navigating the intersection of business needs and technological solutions. Her Bachelor's in Information Systems from Ohio State provided a solid foundation, but it was her early career roles in data analysis and IT support that honed her practical problem-solving skills. She joined her current logistics company eight years ago, initially as a senior analyst, and was promoted to Business Systems Manager six years ago. In this role, she inherited a fragmented landscape of spreadsheets, legacy databases, and rudimentary in-house applications. Olive’s primary focus has been on bringing order and reliability to these systems. She successfully led the migration of customer service intake forms from a paper-based system to a digital workflow tool two years ago, a project that significantly reduced processing time. Currently, she’s pushing for a more substantial overhaul of their exception-tracking process, which is a persistent source of operational friction. She views her team of four as critical enablers of the business, and their output directly impacts the company’s ability to operate smoothly. She's deeply pragmatic, preferring solutions that offer tangible benefits and are manageable within the company’s existing infrastructure and budget. Time is a valuable commodity, both at work and at home, and she often feels the pressure of having too many important tasks and not enough hours to complete them perfectly. Her approach to her career is steady and focused on continuous, albeit deliberate, improvement, rather than rapid, disruptive change. She values stability and predictable outcomes, both for her team and her family’s finances, which are managed with a long-term perspective.

Background & daily life

A day in their life

Olive’s day typically begins around 6:30 AM with coffee while checking urgent emails and the company’s overnight operational status. After getting Maya ready for school, she heads to the office by 8:00 AM. The morning often involves a team stand-up to discuss priorities and roadblocks, followed by a meeting with a warehouse manager to clarify requirements for a new intake form. Lunch is usually a quick salad at her desk while reviewing a draft user guide. The afternoon might include troubleshooting a bug in the dispatch workflow tool with one of her analysts, a planning session for a new reporting module, and responding to a backlog of support tickets. She aims to leave by 5:30 PM to pick up Maya from after-school care, making family dinner the priority.

Lifestyle

Olive and her husband, Mark, a high school history teacher, live in a comfortable, albeit slightly dated, ranch home in a suburban Columbus neighborhood. Weekday evenings are a predictable rhythm of dinner, homework help for their daughter, Maya, and occasionally catching up on emails. Weekends involve youth soccer games, grocery runs, and trying to tackle DIY home projects Mark initiates. She's conscious of her health, aiming for three gym sessions a week, and manages their finances prudently, prioritizing savings for Maya’s college and home renovations. Social life is often centered around family events or casual get-togethers with a small circle of close friends.

Work life

Olive’s workdays are a constant balancing act between proactive system improvements and reactive user support. Her team of four, a mix of junior analysts and a seasoned SQL developer, fields requests from operations and customer service daily. They’re currently wrestling with an inefficient, spreadsheet-heavy exception tracking system that’s prone to data entry errors, which Olive wants to migrate to a more robust, traceable digital solution. She spends a significant portion of her time in meetings, defining requirements for small enhancements to their in-house tools, and troubleshooting issues that disrupt daily dispatch or customer communication. The pressure is to maintain stability while finding opportunities for measurable efficiency gains.

Relationships

Olive is married to Mark, her college sweetheart, and they navigate parenthood with Maya collaboratively. Her parents, retired teachers living nearby, offer occasional support. Professionally, she relies on the operational expertise of warehouse managers and the customer service leads. She has a good working relationship with IT infrastructure, though their priorities often diverge.

How they decide

Olive is primarily a research-heavy decision-maker, especially when it involves new tools or significant process changes. She thoroughly evaluates options, gathers input from her team and stakeholders, and looks for practical, data-supported justifications. She prefers incremental improvements and proven solutions over unproven technologies, but will champion innovation if the business case is strong and the risks are well-managed.

How they sound

Olive speaks with a clear, measured cadence, generally avoiding jargon unless discussing technical specifics with her team or peers. Her tone is professional and patient, even when explaining complex issues. She tends to use straightforward language and values directness, but is always polite. She rarely uses slang and avoids hyperbole, preferring factual statements.

Personality traits

  • methodical
  • detail-oriented
  • proactive
  • resourceful
  • patient
  • analytical
  • calm under pressure
  • organized

Goals

  • Streamline the exception tracking process to reduce manual errors by 30% within the next fiscal year.
  • Develop a comprehensive reporting dashboard that provides real-time visibility into key operational metrics.
  • Achieve higher user adoption rates for newly implemented system upgrades.
  • Mentor her team members to take on more responsibility and grow their technical skills.
  • Maintain a healthy work-life balance that allows for quality family time.

Problems & frictions

  • The current manual processes for tracking operational exceptions are time-consuming and error-prone, leading to downstream issues.
  • Lack of standardized reporting across different departments hinders quick decision-making.
  • The existing in-house tools are aging and becoming difficult to maintain and scale.
  • Limited budget for new software development or significant upgrades puts pressure on leveraging existing resources.
  • Constant requests from various departments for ad-hoc data pulls and report modifications divert team capacity from strategic projects.

Values

  • reliability
  • process clarity
  • accountability
  • practical problem solving
  • efficiency

Interests

  • workflow automation
  • supply chain operations
  • dashboards and reporting
  • process improvement methodologies
  • data visualization

Media habits

  • Reads industry newsletters (logistics tech, business process management)
  • Listens to podcasts during commutes (e.g., 'Supply Chain Now', 'HBR IdeaCast')
  • Follows specific LinkedIn influencers in operations and IT
  • Uses online forums for technical problem-solving
  • Checks business news sites daily

Questions & answers

Olive Koss’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of m-Power Development Platform (https://www.mrc-productivity.com/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make m-Power Development Platform 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).

    Currently, my team and I rely heavily on spreadsheets, SQL views, and a few custom web tools to manage our operations. It's functional, but prone to errors, especially our exception tracking. m-Power's promise of building custom apps and AI tools, potentially replacing spreadsheets and aging systems, is appealing. The ability to build applications quickly and have a team that can assist is a significant draw, especially given our limited resources. However, I'd need to see a clear demonstration of how it integrates with our existing infrastructure and the actual cost, as the pricing basis isn't immediately clear. My maximum acceptable price would be $1,500 per month, assuming it covers unlimited users and applications, based on our need for scalability.
    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.