John Dijkstra

Why this persona fits the audience

He works as operations director at a 50-person Rotterdam logistics startup. He leads a 4-person analytics team that maintains Tableau views for route performance, delivery SLAs, and warehouse throughput, with source data coming from CSV exports and SQL.

• Age: 29
• Location: Rotterdam, Netherlands
• Occupation: Operations Director
• Income: €70k base + bonus
• Education: MSc in Supply Chain Management
• Company size: 50 employees
• Years in role: 2

“Efficiency isn't about moving faster; it's about removing the friction so the right thing happens automatically.”

Born in the industrial port city of Rotterdam, John Dijkstra grew up surrounded by cranes and shipping containers, an environment that subtly shaped his fascination with movement and systems. He pursued an MSc in Supply Chain Management at Erasmus University, where he distinguished himself not just for his academic grades, but for his ability to translate theoretical models into practical, code-based solutions. At 27, he joined a burgeoning logistics startup in the city, initially as a data analyst. Within a year, his proactive approach to cleaning up fragmented data sources and automating manual reporting caught the attention of the C-suite, leading to his promotion to Operations Director. Now 29, John stands at the helm of the company's analytics division, managing a small but agile team of four. His role is less about high-level strategy and more about the gritty reality of keeping the data pipeline flowing. The company operates on a shoestring budget compared to enterprise competitors, meaning John must be the architect, engineer, and operator of their entire data infrastructure. He personally writes the SQL queries that pull data from disparate sources, cleans the CSV exports from legacy carrier systems, and designs the final Tableau visualizations that the board reviews. This hands-on involvement is a necessity born of resource constraints but also a point of pride for John, who believes that true ownership requires understanding the code at the lowest level. John's life is defined by a tension between his natural desire for order and the chaotic nature of startup growth. While he values reliability above all else, his world is constantly shifting as new clients demand new metrics and warehouses expand into new regions. He spends a significant portion of his mental energy fighting entropy—debugging broken filters, reconciling timestamp mismatches, and convincing non-technical stakeholders why a 'quick fix' will eventually break the system. Despite the stress, he finds satisfaction in the precision of his craft. A perfectly rendered dashboard that accurately predicts a delivery delay is his version of art. He is financially secure but frugal, reinvesting his surplus income into his professional development and home improvements rather than luxury goods. His future looks toward building a scalable data culture within the company, potentially transitioning into a Chief Operating Officer role once the organization stabilizes enough to hire dedicated engineering talent.

Background & daily life

A day in their life

John wakes at 5:30 AM, immediately making a single-origin espresso with a precise grind size. By 6:15 AM, he is cycling through the rainy streets of Rotterdam, listening to a podcast on lean manufacturing. He arrives at the office by 8:00 AM, the first one there, and immediately reviews the overnight data sync logs to catch any errors before the team arrives. His morning stand-up is concise, focusing on three critical blockers for the day. He spends the mid-morning debugging a complex SQL join that was distorting the warehouse throughput metrics, then shifts to a meeting with the finance lead to explain a variance in delivery SLAs. Lunch is a quick sandwich eaten at his desk while reading a technical paper on predictive routing algorithms. Afternoon meetings involve reviewing new dashboard prototypes with his analytics team, critiquing their filter logic and color schemes for clarity. He leaves around 6:00 PM, stopping at a gym on the way home to decompress. Evenings are reserved for family time or, occasionally, fine-tuning his espresso setup or watching a replay of a Feyenoord match.

Lifestyle

John lives in a sleek, renovated apartment in Feijenoord, characterized by clean lines and minimal clutter—a physical manifestation of his desire for order. His mornings are ritualistic: he wakes at 5:30 AM to brew a precise double espresso using a manual lever machine, ensuring the water temperature is exact before starting his commute via bicycle along the Maas river. He values health but fits it into a tight schedule, often opting for quick, high-protein meals prepared in bulk on Sundays. Financially, he is conservative; he invests heavily in his retirement fund and avoids unnecessary subscriptions, preferring to pay for tools only if they demonstrably save time or reduce error rates. Socially, he is selective, maintaining a close circle of university friends who share his professional drive, while his weekends are dominated by watching Feyenoord matches or training for local charity runs.

Work life

At the heart of a rapidly scaling logistics startup, John manages the critical flow between strategy and execution. His days are consumed by reconciling messy CSV exports from third-party carriers with internal SQL databases to feed Tableau dashboards. He oversees four analysts who build visualizations for route efficiency and warehouse throughput, but he remains the ultimate gatekeeper of data accuracy. The pressure is constant; a delayed shipment or a misunderstood SLA metric can cost the company significant client trust. He spends hours debugging SQL queries that break during peak load times and frequently mediates between warehouse staff demanding immediate answers and executive leadership seeking long-term trend analysis. His office is a hub of whiteboard scribbles detailing workflow bottlenecks, and he often stays late to ensure the morning reports are flawless.

Relationships

John's primary influence comes from his mentor, a former supply chain VP who now consults for larger EU firms; their weekly calls focus on strategic scalability rather than daily tactics. At home, his partner, an architect, provides a necessary counterbalance to his analytical rigidity, encouraging him to disconnect on weekends. He has a loyal group of five friends from his MSc program, most of whom are also in tech or engineering, forming a tight-knit support network for both career advice and social venting. He is not deeply embedded in the broader Rotterdam business community, preferring to engage through specific industry conferences where he can exchange technical insights rather than make small talk.

How they decide

John is a methodical researcher who prioritizes evidence over hype. He rarely makes decisions based on peer recommendations alone; instead, he demands proof of concept, detailed technical specifications, and clear ROI calculations. If a tool promises efficiency, he will first attempt to replicate its function manually or with free alternatives to benchmark the effort. He is cautious about recurring costs, viewing every subscription as a potential drain on resources unless it solves a critical, recurring bottleneck. His decision process involves consulting his team for user experience feedback but ultimately relies on his own assessment of system stability and data integrity.

How they sound

John speaks in a calm, measured Dutch-accented English, favoring direct sentences over qualifiers. He avoids vague terms like 'maybe' or 'I think,' preferring 'the data indicates' or 'the constraint is.' He rarely uses slang, and when he does, it is strictly professional jargon related to logistics or coding. He tends to pause briefly before answering complex questions to ensure precision. He does not use hyperbole or emotional language when discussing work problems, framing issues as solvable mechanical failures rather than crises. His tone is polite but firm, establishing authority through competence rather than volume.