Why this persona fits the audience
Heads a 2-person open-source program at a cloud startup in Chicago. He manages sponsored issues for a public Terraform provider, coordinates contributors across GitHub Discussions and a spreadsheet, and reports progress back to the core engineering team each sprint.
- Age: 40
- Location: Chicago, Illinois, US
- Occupation: Open-source program manager
- Income: $132,000
- Education: Master's degree in Technical Communication
- Company size: 15-20 employees (Seed/Series A)
- Years in role: 3
“The best open source programs aren't built on code alone; they're built on the invisible architecture of trust, documentation, and consistent communication.”
Wayne Fisher, 40, serves as the de facto architect of open-source culture at a nimble Chicago-based cloud startup. With a Master's in Technical Communication, he uniquely blends the soft skills of diplomacy with the hard skills of infrastructure management. Currently, he leads a lean two-person program dedicated to maintaining a public Terraform provider, a critical tool for the company's customers. His role is less about coding and more about orchestration: he navigates the complexities of GitHub Discussions, manages a growing list of sponsored issues, and acts as the translator between the chaotic energy of the global developer community and the structured demands of the core engineering team. His recent focus has been on stabilizing the contribution pipeline. Last quarter, he identified that manual tracking via a shared Google Sheet was causing payout delays and confusion among contributors. In response, he implemented a rigorous tagging system within GitHub Issues and drafted a new contributor guide that reduced onboarding time by half. Despite these successes, he remains acutely aware of the inefficiencies in his current toolkit. The reliance on disparate systems—Spreadsheets for finance, Jira for engineering, and GitHub for collaboration—creates a constant friction point. He finds himself spending valuable hours reconciling data rather than engaging with the community. Financially, Wayne is pragmatic. Earning $132,000, he views every dollar spent on software as an investment in operational efficiency. He is skeptical of tools that promise to 'solve everything' without a clear path to implementation. His career trajectory is steady; he aims to professionalize the open-source function within his organization, eventually proving that community contributions are a tangible asset class. He is currently evaluating whether his current manual processes can be scaled or if the startup needs to invest in specialized platform software to support its growth, a decision that weighs heavily on his quarterly planning.
Background & daily life
A day in their life
Monday starts with a 7:00 AM walk to clear his head before diving into Slack. By 9:00 AM, he's already in a meeting discussing a stalled pull request for the Terraform provider, where he mediates between a confused new contributor and a busy backend engineer. Lunch is usually a quick sandwich at his desk while he updates the master bounty spreadsheet, manually noting which issues have been claimed and which need reassignment. The afternoon is spent writing a detailed sprint report for the CTO, highlighting the number of hours saved by external devs versus the cost of the bounties paid out. At 4:30 PM, he joins a community call to answer questions about the upcoming release notes, ensuring clarity for everyone involved. Evenings are reserved for family dinner and reading, though he keeps his phone nearby just in case a critical issue pops up. He ends the day by organizing his digital workspace, ensuring tomorrow's to-do list is prioritized.
Lifestyle
Wayne lives in a renovated brick bungalow in Lincoln Park, balancing his career with family life in a household that values structure. His evenings are often split between helping his 8-year-old with math homework and reviewing documentation updates for the Terraform provider. On weekends, he enjoys hiking along the Chicago lakefront or attending local board game nights with friends, seeking low-drama social interaction. Financially, he is conservative; while his income is solid, he avoids unnecessary subscriptions and prefers tools that offer clear, long-term value over flashy features. He maintains a strict work-life boundary, rarely checking emails after 7 PM unless a critical infrastructure incident occurs, preferring to recharge with physical activity or reading non-fiction history books.
Work life
His day revolves around bridging the gap between external contributors and the internal engineering team at their small cloud startup. The workload is intense but manageable due to his systematic approach; he spends mornings triaging GitHub Discussions, updating the master contributor spreadsheet, and drafting status reports. Afternoons are reserved for synchronous meetings with the two other team members and asynchronous reviews of pull requests. The pressure comes from the need to maintain momentum without overwhelming the volunteer community. He uses Jira for internal tracking and Excel for bounty coordination, often feeling the friction of manual data entry when trying to prove ROI to leadership. His immediate boss expects weekly sprint reports that quantify exactly how many hours of engineering time were saved by external contributions.
Relationships
Wayne is married to Sarah, a high school teacher who keeps him grounded in community service outside of tech. Their son, Leo, looks up to Wayne's ability to solve complex puzzles. Professionally, he has a tight-knit circle of three other Open Source Program Managers in the Midwest who meet monthly for coffee to vent about similar struggles. He relies heavily on the informal network of senior contributors to his Terraform project, treating them more like colleagues than volunteers. While he is friendly on LinkedIn, he prefers face-to-face interactions for building trust, often inviting key contributors to lunch in downtown Chicago rather than relying solely on virtual calls.
How they decide
Wayne operates with a cautious, evidence-based decision-making style. He is not swayed by marketing slogans or aggressive sales tactics; instead, he requires concrete data, peer testimonials, and proof of concept before committing resources. He typically conducts a thorough review of existing workflows, identifies specific pain points, and then researches solutions that directly address those gaps. He values transparency and clear pricing models, often delaying decisions until he can consult with his engineering lead or compare options against current free alternatives. Once convinced, he moves quickly to implement, provided the integration effort is low.
How they sound
Wayne speaks with a calm, Midwestern cadence—measured, precise, and devoid of unnecessary jargon. He favors complete sentences and often uses analogies related to logistics or construction to explain technical concepts. He avoids hyperbole, rarely saying 'revolutionary' or 'game-changing,' preferring terms like 'efficient,' 'scalable,' or 'reliable.' When frustrated, he doesn't raise his voice but becomes more terse and focused on the process breakdown. He frequently uses phrases like 'Let's look at the data' or 'What does the spec say?' He respects brevity but insists on context, often asking follow-up questions to ensure all stakeholders are aligned before moving forward.
Personality traits
- Meticulously organized
- Process-oriented
- Diplomatic
- Data-driven
- Patient educator
- Skeptical of hype
- Structured communicator
- Community-focused
- Time-conscious
- Pragmatic
Goals
- Standardize the contribution workflow to reduce administrative overhead by 20%
- Increase the diversity of active contributors to the Terraform provider
- Publish a comprehensive case study on their open-source success for industry recognition
- Secure a larger budget for community bounties to accelerate feature delivery
- Mentor junior developers on effective open-source communication
- Transition from manual spreadsheet tracking to an automated platform
Problems & frictions
- Tracking bounties and payouts manually in spreadsheets leads to frequent version control errors
- Difficulty quantifying the financial ROI of community contributions for executive stakeholders
- Contributors often abandon tasks mid-way due to unclear scope or lack of timely feedback
- Managing conflicting priorities between urgent bug fixes and long-term feature development
- Communication silos between the remote community and the co-located engineering team
- Lack of a centralized dashboard to visualize contributor health and engagement trends
Values
- coordination
- accountability
- community growth
- documentation
- transparency
Interests
- Terraform
- developer relations
- project reporting
- community operations
- infrastructure as code
Media habits
- Weekly 'Changelog' podcast
- GitHub issue threads and comments
- Substack newsletters on DevRel trends
- Reddit r/devops and r/Terraform
- LinkedIn technical deep dives
- Local Chicago tech meetups