This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Spargle meets Jan-Hermen Ploeg
Book: ‘A little life‘, by Hanya Yanagihara
Documentary: ‘OJ: Made in America‘, by Ezra Edelman
“I’m someone who enjoys solving real-world problems and being hands-on.”
What is your role?
I’m a Product Manager working through Spargle, currently assigned to develop a logistics software solution. In my role, I work on discovering and delivering a digital platform that helps optimize supply chain operations, providing better visibility and coordination across logistics networks.
My background is primarily in software development rather than logistics, but in my work I use product management frameworks and methodologies which are industry agnostic. Having the experience of applying these frameworks across different industries helps me to get up to speed very quickly when working in an industry which is new to me.
I specialize in building internal systems and applications for large organizations – the kind of software that powers operations behind the scenes rather than consumer-facing products. I find it incredibly rewarding to work for internal users, as I feel a strong sense of empathy for their needs. It’s exciting to collaborate closely with them throughout the development process and see firsthand how the software makes their work easier and more efficient.
I read that you studied history. What made you switch to technology?
Yes, I started with history, but I ended up finishing International Business and Management Studies in Groningen. While I found history fascinating, I realized I wanted to pursue something more practical and directly applicable to the world around me. I’m someone who enjoys solving real-world problems and being hands-on, and Business and Management studies suited me much better. In addition to this, the program offered me the opportunity to study at the Plekhanov Russian University of Economics in Moscow for 1 year which was an incredible experience that broadened my perspective.
That’s my formal background, but informally, I was always coding on the side as a hobby. In the end, my career path was shaped more by my informal background than my academic studies. I chose my first job based on what I enjoyed doing on my own – coding and building things – rather than what I formally studied.
Would you say your hobby became your job?
In a way, yes. I’ve always been interested in software development and the creative process of building software products. What I enjoy most is the collaborative aspect – working with a team to bring ideas to life. It’s rewarding to see something you’ve helped create make a real impact and see users benefit from it.
“It’s simple really: when developers understand the business problems, and business people understand what’s technically possible, we make better products together.”
What is your biggest challenge within your role?
The biggest challenge right now is ensuring the entire team stays aligned and focused on a shared goal. With team members distributed across the globe in different time zones and coming from diverse backgrounds, achieving a common understanding can be a challenge. This setup requires extra effort to maintain clear communication and alignment, but it’s something we’ve been working hard on. It’s incredibly important that everyone feels connected to the larger vision, despite the distance, so we can work jointly toward our objectives.
I can imagine that. You said communication is one of the ways you’re solving this, how do you foresee that evolving in the future?
Yes, though I think it is not only about communication; it’s also about setting clear goals and ensuring everyone has access to the right information. For example, it’s important to give people visibility into what we’re doing in the short term (the next two weeks), midterm (this quarter), and long term (the next year).
There’s a great framework for this that I think would be helpful to share – it’s called The Decision Stack, created by Martin Eriksson. It connects goals across different timelines, linking a high-level vision (perhaps a five-year objective) all the way down to the specific tasks a team is working on this week. It also loops back up, ensuring that day-to-day work directly contributes to the bigger picture. This kind of clarity not only improves alignment but also gives the team a sense of purpose and direction.
What trends do you foresee for next year?
I think software engineers will take on a much more prominent role in communicating with users, choosers, and internal stakeholders. As AI takes over routine coding tasks, engineers will have more capacity to focus on understanding the problems that need solving and designing effective solutions. This means their role in the discovery phase will expand. Engineers won’t just be builders – they’ll be co-creators of the solution and will act much more as creative partners.
That’s interesting, because my impression of developers is that they often work in isolation. So, you’re saying there’ll be more collaboration?
Yes, collaboration is essential in software development. While developers need focused time to write code, their expertise is invaluable during the entire development process. I actively involve engineers in key meetings, especially during problem identification and solution design phases.
If developers spend all their time just writing code, they’re only delivering about half of their value. The other half comes from their insights during problem discovery and solution design. When engineers participate in these strategic discussions, they bring technical perspective to business challenges early on, which leads to more innovative and effective solutions.
So, you need an interdisciplinary approach to make sure everyone’s aligned?
Yes, and I see product management changing in an important way. We’re moving beyond just connecting business and tech teams – we’re becoming better at bringing people together to solve problems.
The real value of a product manager today is in getting developers involved earlier, before we start building. Instead of just collecting requirements and managing timelines, we create an environment where developers and business people can work together to find the best solutions. This means running better meetings and workshops where everyone feels comfortable sharing their ideas and expertise.
It’s simple really: when developers understand the business problems, and business people understand what’s technically possible, we make better products together.
“It’s rewarding to deliver results that make a real difference. That’s what drives me – coming in, understanding what needs to be fixed, and helping the company move forward.”
What motivates you in your work?
I enjoy working as an external product manager because companies hire us when they need help right away. This means my work has a very clear purpose – I’m there to solve a specific challenge that needs immediate attention.
This setup really motivates me. When a company hires me, it’s because they need extra help or expertise they don’t have in-house right now. I can focus completely on solving their problem, and I find it rewarding to deliver results that make a real difference for the company. That’s what drives me – coming in, understanding what needs to be fixed, and helping the company move forward.
Do you usually work with big companies, or do you work with smaller ones too?
I’ve had the opportunity to work with companies of all sizes – from 10 people to 100,000. Right now, I’m working for an organization which has about 1,300 people. It’s a perfect size – large enough to have ambitious goals, yet small enough to maintain an informal and agile atmosphere. Their goal is to deliver a significant software product, and that mix of speed and ambition is really exciting to work with.
What’s your favourite book?
Oh, I’d have to think about it because there are so many. For books, I both read fiction and non-fiction. When it comes to fiction, I really like American writers because they’re fantastic storytellers, and if I had to pick a favorite title it would probably be A Little Life by Hanya Yanagihara. I read it four years ago, and I still think about it now and then – the characters just stay with you. It’s such an immersive book.
Lately, though, I’ve been getting into biographies. For example, there’s a great one about Martin Luther King that I read recently. While fiction can sometimes feel like a piece of art you have to work for, non-fiction, like a well-written biography, often feels more accessible. The author’s goal is to simply tell you the story, like with Martin Luther King, making it easier to relax while reading.
Do you have a favourite documentary?
When it comes to documentaries, I used to volunteer at IDFA, a documentary festival, some time ago. That’s where I learned that documentaries can serve as either microscopes or weapons, and I prefer the microscopes. I’m drawn to the fly-on-the-wall, observational style. One that comes to mind is OJ: Made in America by Ezra Edelman. It’s about eight hours long.
Wow, did you watch it all in one go?
Almost, yeah! I really liked it. It doesn’t try too hard to make a point; it just shows you something, letting you take it all in. It’s about OJ Simpson, his famous murder case, but it also dives into racial tensions in America and touches on society in the ’60s, ’70s, and ’90s. It’s really fascinating.
Ezra Edelman recently made a similar long documentary, about nine hours, on Prince, who happens to be one of my favourite artists. It is near completion but unfortunately, Prince’s estate is suing to prevent it from being shown. Apparently, Prince had a darker side they don’t want people to see, and they’re afraid it might darken his image. Still, what a project to pull off something like that.
