Logan van der Linden

Why this persona fits the audience

Operations manager at a 14-person digital agency in Amsterdam. He triages client bug reports in HubSpot, turns engineering work into GitHub Issues for two developers, and keeps the queue organized in a shared doc for the account team.

• Age: 40
• Location: Amsterdam, Netherlands
• Occupation: Operations manager
• Income: €60k-€75k
• Education: BSc Business Administration
• Company size: 14
• Years in role: 6

“If you can't measure it, you can't fix it, but if you spend all day measuring, you're just watching paint dry.”

Logan van der Linden, 40, is the operational backbone of a 14-person digital agency in Amsterdam, a role he has held for six years after transitioning from a general administration background. With a BSc in Business Administration, he combines administrative discipline with a deep understanding of software development lifecycles. Living in a renovated canal house in Oud-West with his partner, Logan leads a life defined by structure and purposeful minimalism. His income of €65,000 reflects his mid-level management status, allowing him financial security but necessitating careful budgeting for home renovations and savings. Professionally, Logan is the gatekeeper between client expectations and developer output. His days are consumed by the meticulous task of triaging bug reports in HubSpot, where he must distill vague client frustrations into actionable GitHub issues for the two developers on staff. He maintains a complex, shared documentation system that serves as the agency's central nervous system, ensuring the account team remains aligned with engineering progress. Despite the simplicity he values, his reality is a constant battle against information silos and manual sync errors. He recently decided to implement a stricter version control policy for documentation to reduce confusion, a move that required significant buy-in from the team. Logan finds satisfaction in systems that run themselves, viewing any manual intervention as a temporary failure of design rather than a necessary routine. His world is one of calculated order, where every minute saved on data entry is reinvested into strategic planning.

Background & daily life

A day in their life

Logan wakes at 6:15 AM, makes black coffee, and checks the weather. By 7:00 AM, he is cycling through the canals, listening to a podcast about process optimization. At 8:30 AM, he arrives at the office, immediately opening HubSpot to triage overnight tickets. He spends the morning translating client emails into GitHub issues, carefully tagging priorities and attaching screenshots. Lunch is a quick sandwich eaten while reviewing the shared status document for the afternoon client call. Afternoon meetings are focused on aligning the account team with the dev roadmap. He leaves at 5:30 PM sharp, avoiding overtime unless absolutely necessary. Evenings are for cycling or cooking, keeping his mind away from work screens until bedtime.

Lifestyle

Logan lives in a modest but character-filled apartment near the Prinsengracht, sharing rent with his partner, an architect. His evenings are reserved for physical activity; he cycles to work regardless of the rain, treating it as non-negotiable maintenance. He manages his finances with a strict budget, prioritizing savings over luxury, often cooking elaborate meals from scratch to save money on dining out. Socially, he is selective, preferring deep conversations with a small circle of close friends over large gatherings. His weekends are structured around long bike rides through the countryside or restoring old furniture, activities that require patience and precision rather than spontaneity.

Work life

At the heart of the agency's chaos stands Logan, acting as the central nervous system between clients and the two core developers. His day begins by clearing the HubSpot inbox, where he translates vague client complaints into precise technical tickets for GitHub. He maintains a master spreadsheet that serves as the single source of truth for the account team, ensuring no request slips through the cracks. The pressure is constant: balancing the urgency of client deadlines with the need to protect the developers' coding flow. He spends hours refining processes and documenting workflows, believing that a well-documented system is the only way to scale without losing quality.

Relationships

Logan is married to Sarah, who works remotely as a graphic designer; they rely on each other for emotional grounding amidst chaotic workweeks. He has two close friends from university who meet him for coffee once a month to discuss politics and cycling. His professional influence comes from a former boss who taught him the value of 'quiet efficiency,' and he occasionally seeks advice from a local operations consultant regarding scaling challenges. He is not deeply embedded in the broader Amsterdam expat community, preferring the stability of his established local network.

How they decide

Logan approaches decisions with a cautious, evidence-based methodology. He rarely acts on impulse or peer pressure, preferring to gather data, test small pilots, and verify reliability before committing resources. He values autonomy and self-sufficiency, often trying to solve problems internally with spreadsheets or scripts before considering external tools. When he does evaluate new solutions, he scrutinizes the integration capabilities and long-term maintenance requirements more than the marketing claims, seeking a tool that disappears into the workflow rather than demanding attention.

How they sound

Logan speaks in a calm, measured Dutch-accented English, favoring direct sentences over flowery language. He avoids jargon unless defining it, and rarely uses exclamation points in writing. His tone is professional yet approachable, often pausing to clarify context before answering. He tends to use phrases like 'Let's look at the data' or 'What's the bottleneck?' rather than emotional appeals. In conversation, he listens more than he speaks, nodding thoughtfully before offering a concise, solution-oriented response.