Justyna Pindel avatar

Justyna Pindel

Executive MBA | Agile Practitioner | Product Facilitator

Last trained 3 days ago

About Justyna Pindel

Justyna Pindel is an Executive MBA Agile Practitioner and Agile & Lean Coach based in Belgium, currently coaching product and engineering teams at EPI Company while building scalable burnout prevention solutions. She specializes in designing sustainable company culture, Agile methodologies, and Systems Thinking, integrating neuroscience and leadership facilitation to drive organizational change. Her credentials include an Executive MBA, Professional Scrum Master I certification, three published books on Agile and Kanban, and experience scaling the ACE! Conference to over 500 international practitioners.

Frequently asked

How do you prepare for uncertainty in product planning?

Map out plausible futures by identifying two critical uncertainties, each with contrasting outcomes. Define concrete signals that help you recognise which scenario is unfolding, then agree on responses before you need them. This turns abstract uncertainty into something actionable—you can't predict the future, but you can prepare for several possible versions of it.

What is the minimum viable product approach and how do you apply it?

Start by defining what success actually requires—the absolute essentials without which your product or project cannot exist. Use MoSCoW prioritisation to separate Must Haves from Should, Could, and Won't Have items. Then focus your effort on delivering the Must Haves first, using the Cost of Delay to determine which decisions are time-sensitive and belong at the top of your backlog.

How should a product manager approach design and user research?

Begin with user research before jumping to solutions. Create personas, map user journeys, and understand how people actually live and work—not how you imagine they do. Only after you understand the real context and needs do you translate them into concrete requirements. This prevents designing for an imaginary version of your users and ensures your solutions address actual problems.

What is a retrospective and how can it improve teamwork?

A retrospective is an intentional conversation where a team looks back at a period—a sprint, a project, or a month—to celebrate what went well, identify what was difficult, and decide what to improve. It creates dedicated space for conversations that might not happen otherwise. Regular retrospectives prevent small frustrations from becoming bigger problems and keep teams aligned on continuous improvement.

How do you manage shared projects and goals with another person?

Create a weekly meeting with clear structure: check in personally, review individual progress that affects shared life, move through project updates, and always leave time for items that need discussion. Use tools like a shared Notion board, a shared kitchen calendar, or a simple notebook to keep everything visible. Regular synchronisation prevents misunderstandings from growing and keeps both people aligned on priorities.

What is the best way to delegate responsibility in a project?

Delegate ownership of outcomes, not just tasks. Be clear about what success looks like and what budget or constraints exist, but let the other person decide how to achieve it. Use a RACI matrix to make responsibilities explicit, then step back. People do their best work when they own the result rather than simply executing instructions.

How do you apply Agile practices to complex non-work projects?

Treat any complex project—a wedding, building a house, life planning—like a product. Use user story mapping to understand different perspectives, build a backlog of everything needed, define your Minimum Viable version of the product, and prioritise using frameworks like MoSCoW. The same thinking that works in product development works anywhere you're making trade-offs and managing uncertainty.

What makes remote-first teams different and how should you lead them?

Remote-first teams have no shared history of coffee breaks, hallway conversations, or spontaneous interactions—they must build trust and psychological safety intentionally through regular, structured communication. Work with real people, not avatars. Invest in one-on-one connections, create space for genuine conversation, and ensure collaboration happens by design, not by accident.

Straight from the source

“Critical Uncertainties isn't about predicting which future will happen. It's about being less surprised by the possibilities, recognising when you're moving into a particular scenario, and having a few ideas about what to do next.”

“Product management isn't about producing documents. It's about asking better questions before committing to a solution. It's about understanding people, making trade-offs explicit, and creating the conditions for better decisions.”

“I delegated ownership, not just tasks. Each person knew what they owned, who they needed to work with, and what success looked like. They didn't need to ask me how to do it. They needed to achieve the outcome. And that distinction made all the difference.”