Why this persona fits the audience
Leads a 5-person support team that records bug reproductions, quick demos, and internal process clips for ticket handling. He is responsible for keeping the workflow simple, and the team currently mixes Snagit, Slack clips, and spreadsheet tracking.
- Age: 45
- Location: Chicago, Illinois, USA
- Occupation: Support Operations Manager
- Income: $105,000/year
- Education: Bachelor's degree
- Company size: 200 employees
- Years in role: 5
“My job is to make sure the wheels keep turning smoothly, so everyone else can do theirs effectively.”
Gregg Deckow, 45, has carved out a niche for himself as a Support Operations Manager in the fast-paced SaaS industry, a role he's held for the past five years at his current company in Chicago. His journey into operations management wasn't a straight line; after earning his Bachelor's degree in Business Administration, he spent several years in various customer-facing support roles, where he developed a keen eye for process inefficiencies and the critical need for clear, actionable documentation. This hands-on experience fueled his drive to move into a role where he could proactively shape how support information was created and utilized. He's deeply committed to his team of five, viewing them as the engine for creating essential assets like bug reproductions, quick demos, and internal process guides. Gregg's philosophy centers on simplicity and accountability; he believes that a well-defined, easy-to-follow workflow is paramount, even if it means wrestling with a current patchwork of tools like Snagit, Slack, and spreadsheets. He's not one for grand gestures or chasing the latest tech trends without due diligence. Instead, Gregg is a pragmatist, focused on tangible improvements that enhance team efficiency and product understanding. His income of $105,000 allows for a comfortable life, but he remains a prudent saver, prioritizing his children's education and long-term financial security. He sees time as a valuable, finite resource, both for himself and his team, and is constantly looking for ways to optimize its use. Status, for Gregg, is less about titles and more about the quiet satisfaction of a well-oiled operation and a team that consistently delivers high-quality results.
Background & daily life
A day in their life
Gregg's typical weekday begins with a quick scan of urgent emails and Slack messages before his 8:30 AM stand-up with his support operations team. The morning is often a mix of reviewing bug reproduction tickets, approving demo scripts, and troubleshooting any immediate workflow blockers. He dedicates a block of time mid-morning to analyzing team performance metrics from their spreadsheets. After lunch, he might have a sync with a product manager about upcoming feature documentation needs or a meeting with engineering to clarify bug details. The afternoon often involves planning future documentation projects, reviewing team member work, and responding to less urgent requests, aiming to wrap up by 5:30 PM.
Lifestyle
Gregg resides in a well-established suburban neighborhood outside Chicago with his wife, Sarah, and their two children, a sophomore in high school and a freshman. His evenings are typically spent helping with homework, attending a school event, or catching up on a sports game. Weekends often involve family outings, yard work, or a round of golf with friends. He's mindful of his finances, preferring to save for future goals like college tuition and retirement rather than impulsive purchases. He values his downtime, often using it to read industry articles or plan upcoming team initiatives.
Work life
As the Support Operations Manager, Gregg's primary focus is optimizing the efficiency and effectiveness of his five-person team. They are the backbone for creating crucial internal documentation: recording step-by-step bug reproductions for engineering, assembling quick demo videos for sales enablement, and producing internal process clips for consistent ticket handling. Gregg is constantly evaluating their current toolset, which involves a patchwork of Snagit for screen recordings, Slack for quick sharing, and spreadsheets for tracking progress and metrics. He feels the pressure to keep the workflow streamlined and the output high-quality, despite the disparate tools.
Relationships
Gregg is married to Sarah, a nurse, and they have a strong, collaborative partnership. He's close with his children, though navigating their teenage years presents new challenges. His core group of friends consists of a few college buddies and fellow golf enthusiasts. Within the company, he has a good working relationship with the Head of Customer Support and the Engineering leads, who rely on his team's bug reproductions.
How they decide
Gregg is a methodical and research-oriented decision-maker. He prefers to gather data, consult with his team, and understand the long-term implications before committing to a change. He values practicality and proven results, often looking for case studies or testimonials from similar organizations.
How they sound
Gregg speaks in a clear, measured tone. He tends to be direct and avoids jargon when possible, preferring straightforward explanations. His cadence is steady, and he rarely raises his voice, even when discussing challenges. He uses phrases like 'Let's look at the data,' 'What's the process here?', and 'We need to ensure consistency.' He avoids overly casual slang or effusive praise, opting for professional and factual communication.
Personality traits
- detail-oriented
- organized
- collaborative
- results-driven
- calm under pressure
- loyal
- straightforward
- methodical
Goals
- Achieve a measurable improvement in ticket resolution time through better internal documentation.
- Develop a more integrated and user-friendly toolchain for his support operations team.
- Mentor and grow the skills of his direct reports, fostering a strong team culture.
- Successfully implement a new internal knowledge base system within the next fiscal year.
- Maintain a healthy work-life balance to be present for his family.
Problems & frictions
- The current mix of tools for creating and managing support documentation is inefficient and prone to version control issues.
- Finding time to thoroughly vet and implement new tooling amidst daily operational demands.
- Ensuring consistent quality and adherence to process across all team members' recordings and clips.
- Communicating the value and impact of support operations improvements to upper management.
- Balancing the need for detailed documentation with the urgency of resolving customer issues.
Values
- process
- accountability
- team efficiency
- reliability
- fairness
Interests
- support tooling
- ticket workflows
- SaaS operations
- process improvement
- team management
Media habits
- industry blogs
- podcasts on management
- local news
- sports news