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

Kannan Asan

Kannan Asan

Agency design operations coordinator

Full-depth AI personas

Why this persona fits the audience

Coordinates a 7-person web design team delivering quick-turn client landing pages and pitch decks. Keeps prompts, screenshots and source URLs in shared docs so designers can recreate sections in Figma and hand off to Webflow or Framer.

  • Age: 33
  • Location: Mumbai, India
  • Occupation: Design operations coordinator
  • Income: ₹16 lakh
  • Education: Bachelor of Commerce
  • Company size: 12-15 employees (small creative agency)
  • Years in role: 2
“I don't just manage people; I manage the invisible architecture that lets creativity happen without it collapsing under its own weight.”

Kannan Asan is a 33-year-old Design Operations Coordinator based in Mumbai, India, earning ₹16 lakh annually. With a Bachelor of Commerce degree, he found his true calling not in traditional accounting, but in the structural organization of creative digital agencies. Currently leading operations for a mid-sized firm, he coordinates a seven-person team responsible for rapid-turnaround landing pages and investor pitch decks. His role is pivotal; he is the bridge between chaotic client demands and precise technical execution. Kannan has built a reputation for creating robust documentation systems where prompts, screenshots, and source URLs are meticulously cataloged, allowing designers to instantly replicate sections in Figma and hand them off to Webflow or Framer without friction. His personality is defined by high conscientiousness and moderate neuroticism; he thrives on order and finds genuine satisfaction in streamlined workflows. While he enjoys the aesthetic side of design, his primary passion lies in the mechanics of how a team ships products. Recently, he made the strategic decision to migrate the team away from scattered Google Drive folders to a centralized, tagged database system, a move that initially faced resistance but ultimately reduced retrieval time by 30%. He is skeptical of 'magic button' solutions that promise to replace human oversight, believing that AI should augment, not automate away, the critical thinking required in operations. Living with his wife and young son in Bandra West, Kannan balances a demanding career with a commitment to being present at home, viewing his financial discipline as a means to secure his family's future rather than a sign of frugality. He is constantly evaluating tools that can reduce the administrative overhead of his job, seeking practical improvements that allow his team to focus more on design and less on searching for files.

Background & daily life

A day in their life

Kannan wakes at 6:00 AM, prepares breakfast for his son, and checks the weather for Mumbai's unpredictable rain. By 8:15 AM, he is on the local train, reviewing his Trello board for the day's critical path items. At the office, his first hour is dedicated to the 'Shared Ops Doc,' where he archives yesterday's winning designs and tags today's client briefs with specific Figma component IDs. Around 11:00 AM, he facilitates a stand-up meeting, clarifying ambiguous instructions from a client who sent a voice note instead of text. The afternoon is spent debugging a Webflow export issue for a pitch deck due at 5:00 PM, coordinating with the lead designer to fix a broken grid. He leaves by 7:00 PM, takes the evening train home, and spends dinner screen-free with his family. Evenings are reserved for reading industry blogs or experimenting with a new no-code automation script, winding down around 10:30 PM.

Lifestyle

Kannan lives in a compact, sunlit two-bedroom apartment in Bandra West, chosen for its proximity to his office and the school for his toddler. His mornings begin at 6:00 AM with a strong filter coffee and checking his son's nursery app before the Mumbai monsoon traffic even begins. He is health-conscious but pragmatic, favoring home-cooked meals over expensive gym memberships, though he tries to walk 5,000 steps daily. Financially, he is disciplined, allocating a significant portion of his income toward his child's education fund and emergency savings, avoiding flashy luxury goods in favor of reliable technology and quality time. Socially, he maintains a tight circle of five close friends from college, preferring intimate dinners over large parties, and often uses weekends to disconnect completely from work screens.

Work life

As the operational backbone of a seven-person design team, Kannan's day is a constant balancing act between creative chaos and rigid structure. He manages a centralized 'Source of Truth' document where every prompt, screenshot, and reference URL for current projects is logged, ensuring that when a designer starts a task, they aren't hunting for assets. His reality involves bridging the gap between the abstract requests of sales teams and the pixel-perfect execution required by the designers. He spends hours troubleshooting why a Figma component didn't export correctly to Webflow or reformatting messy client feedback into actionable tickets. The pressure is high due to tight deadlines for pitch decks, requiring him to be the first line of defense against scope creep while keeping morale high among the creatives.

Relationships

Kannan is deeply connected to his wife, Priya, who works as a marketing consultant; their partnership is built on mutual respect for each other's professional challenges. He is an active member of a local fathers' group in Mumbai, which provides a rare outlet for non-work conversation. His influence comes from his senior agency partner, who mentors him on business strategy, and a network of peers in global design ops circles on LinkedIn. He rarely seeks validation from strangers, preferring the quiet approval of his immediate team when a process runs smoothly.

How they decide

Kannan approaches decisions with a methodical, evidence-based mindset. He does not make impulsive purchases, especially regarding software, viewing them as investments rather than expenses. Before adopting a new tool or changing a workflow, he typically conducts a small-scale pilot with a single team member, gathers quantitative data on time saved, and reviews qualitative feedback. He values peer recommendations from trusted colleagues over marketing hype, and he is willing to invest time in learning a new system if the long-term efficiency gains are clearly demonstrated.

How they sound

His speech is measured, articulate, and distinctly professional yet warm, reflecting his background in commerce and exposure to corporate environments. He avoids overly technical jargon unless speaking with developers, preferring clear, action-oriented language like 'Let's standardize this' or 'We need to lock this down.' He rarely raises his voice, even when stressed, opting instead for concise, direct questions. In casual settings, he might use a mix of English and light Marathi slang, but his core vocabulary remains focused on logistics, timelines, and outcomes.

Personality traits

  • hyper-organized
  • calm under pressure
  • meticulous about version control
  • pragmatic technologist
  • diplomatic mediator
  • system-thinker
  • time-conscious
  • detail-oriented
  • quietly authoritative
  • resourceful

Goals

  • Reduce project handoff time by 20% through better documentation templates
  • Transition the entire team to a unified Figma-to-Webflow workflow without data loss
  • Secure a promotion to Head of Operations within the next 18 months
  • Build a proprietary library of reusable UI components for the agency
  • Achieve financial stability to send his son to an international school by age six
  • Learn advanced React logic to better understand developer constraints

Problems & frictions

  • Fragmented information sources where client assets get lost in email threads
  • Inconsistent file naming conventions causing confusion across the 7-person team
  • Time-consuming manual recreation of complex sections from static screenshots
  • Difficulty tracking which version of a prompt generated which specific output
  • Client revision loops that start because the initial brief was too vague
  • Burnout risk due to the sheer volume of administrative coordination tasks

Values

  • coordination
  • timeliness
  • shared standards
  • clarity
  • efficiency

Interests

  • agency workflows
  • Webflow
  • presentation design
  • no-code automation
  • minimalist productivity systems

Media habits

  • Daily consumption of Indian tech newsletters like Inc42 and YourStory
  • Curates specific Twitter/X lists for Webflow/Framer updates
  • Watches YouTube tutorials on AI tools during commute
  • Reads Medium articles on remote team management
  • Subscribed to niche Slack communities for designers

Questions & answers

Kannan Asan’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of UX Magic (https://uxmagic.ai/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make UX Magic 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, we meticulously document everything in shared documents – prompts, screenshots, source URLs – so our designers can recreate sections in Figma and then hand them off to Webflow or Framer. UX Magic's ability to clone URLs and generate editable Figma files from prompts or screenshots sounds promising for reducing that manual recreation effort. However, I'd need to see how well it handles our specific client needs for quick-turn landing pages and pitch decks. The potential for it to automate away critical thinking in operations is a concern. I'd be willing to try a pilot, perhaps paying up to $30 per month, but it would depend heavily on demonstrated efficiency gains for our team.
    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.