Ana Stefan

5 lessons distance taught me about trust, as a co-founder building from two different cities. Thomas and I live in different cities. Distance challenges most teams. For us, it built the foundation of trust. Here’s what I’ve learned: 1️⃣ Know each other deeply. Don’t stop at roles and skills. Understand values, fears, and motivations. That’s where real alignment starts. 2️⃣ Share the whole picture. We normalize talking about struggles: personal and professional. Because what happens in life shapes what happens at work. 3️⃣ Protect connection time. We spend one full day together every month. It keeps us aligned beyond the operational noise. 4️⃣ Create space to reflect. On workations, we run, think, and debrief. That’s where ideas deepen and clarity returns. 5️⃣ Build trust through consistency. It’s not declared: it’s earned, repeated, and proven. Trust compounds through action. At the end of the day we might live in two cities. But we have one joint mission. And a partnership built on trust. 👉 How do you keep trust strong when distance or pressure tests it? 🔁 Repost to help more founders think with clarity. 💡Follow Christian Rebernik for insights on leadership and performance.

65

39 Kommentare

𝐀𝐠𝐢𝐥𝐞 𝐕𝐚𝐥𝐮𝐞 #𝟒 – 𝐑𝐞𝐬𝐩𝐨𝐧𝐝𝐢𝐧𝐠 𝐭𝐨 𝐂𝐡𝐚𝐧𝐠𝐞 𝐎𝐯𝐞𝐫 𝐅𝐨𝐥𝐥𝐨𝐰𝐢𝐧𝐠 𝐚 𝐏𝐥𝐚𝐧 Let’s be honest—things don’t 𝐚𝐥𝐰𝐚𝐲𝐬 go as planned. You can plan everything perfectly… But then a client changes their mind. The market shifts. Your team hits a blocker. In traditional project management, that used to feel like failure. But in Agile, 𝐢𝐭’𝐬 𝐞𝐱𝐩𝐞𝐜𝐭𝐞𝐝—𝐚𝐧𝐝 𝐞𝐦𝐛𝐫𝐚𝐜𝐞𝐝. One thing I’ve learned as a project manager is that 𝐟𝐥𝐞𝐱𝐢𝐛𝐢𝐥𝐢𝐭𝐲 𝐢𝐬 𝐩𝐨𝐰𝐞𝐫. The ability to adjust quickly, regroup, and realign can save a project from crashing. Agile teaches us to: -Adapt when things shift -Listen to feedback in real-time -Focus on what’s working—and let go of what’s not Because it’s not about following a plan blindly. It’s about delivering value, no matter how the road twists. Planning is good. But being ready to change when it matters? That’s leadership. Have you ever had to scrap a perfect plan to make space for a better outcome? Let’s talk in the comments 👇🏾 #AgileValue4 #RespondingToChange #AgileLeadership #SamuelBoatengOsei #ProjectManagementTips #SamTheProjectManager

61

54 Kommentare

Last week, our team hit what felt like a wall.We kept asking: “Why don’t we have a product roadmap?" And if I'm honest, we were asking not only out of curiosity, but maybe out of blame. And maybe a small amount of frustration/panic. We’re building something ambitious. Ultimately, we want to deliver what's in that screenshot below. Marketers using plain english to run cross-channel analyses, build media plans, forecast revenue, adjust creatives, optimize campaigns... you name it. Even without understanding the technical nuance, I know developing a platform like this means our engineering teams are moving incredibly quickly and doing really hard things. It’s technically complex, but even executed perfectly, our code isn't a deep moat - not for long, anyway. And that speed of development and speed of change felt impossible to plan around, mostly because we were chasing the wrong kind of planning. We wanted to plan for certainty, when we should have been planning for belief. I'll credit a moment of clarity to the whole team settling in to solve the problem together, but especially to our CTO, Vikas Mishra who pointed out: We aren’t missing a roadmap. We were just chasing the wrong kind. So we reframed the question:   👉 Not “Why don’t we have one?” 👉 But “What kind of roadmap can we believe in?”Here’s what emerged: ✅ Layered horizons – what’s locked, what’s likely, what’s still visionary ✅ Time-bound themes – what we’re validating this quarter, not fixed feature lists ✅ Principles-first planning – problems we’re committed to solving, not features we might drop next sprint And just like that momentum returned. We started creating content, marketing the vision, building early pipeline and leading with transparency (this post is exhibit A). If you're caught in that same loop—no roadmap, no progress—ask yourself: Are you truly unable to plan? Or just afraid to plan imperfectly?

48

10 Kommentare