A decade ago, Slash began as a tight-knit engineering team balancing client delivery with a genuine belief that culture, community, and craft could coexist. Today, as a global AI-first digital studio, those foundations are still what hold everything together.
In this session, Peter, Scrum Master and Agile Coach at Slash, will share 10 hard-won lessons on clear communication across cultures, what no Agile framework can actually fix, and why the most important thing at Slash has never been the process.
Q1: The Flashback
“When you first joined Slash, what did you honestly think this place was going to be, and how far off was your initial guess?”
Honestly, when I first joined Slash, I was a bit confused and expected it to be just a standard software solutions company where you receive tickets, write code, and deliver features. But actually, it was much more than what I initially guessed. I quickly realized that Slash was far more dynamic and community-driven. It wasn’t just about output; it was about culture, deep collaboration across countries, and taking real ownership of the value we build together.
Q2: The Global & Remote Reality
“After years of working remotely across different cultures, languages, and time zones, what’s the biggest lesson you’ve learned about making global teamwork actually work?”
The biggest lesson I’ve learned is the power of clear communication while always assuming positive intent. When you work across different cultures and language barriers, your messages can easily be misinterpreted. By keeping communication explicit and clear, and starting from a place of assuming everyone is trying their best to deliver great work, you eliminate misunderstandings and build trust.
Q3: Real Talk on AI
“Now on AI. Where do you land on AI right now? How much has it actually evolved into your daily routine and workflow?”
I’m fully aligned with using AI as a daily partner rather than just a trend. I use tools like ChatGPT, Gemini, and Claude in my daily routine for drafting, refining messages, analyzing retrospective themes, or brainstorming agile practices. AI has truly become a core part of my workflow by handling the heavy lifting on drafting and organizing.
Q4: Product Evolution
“What’s the single biggest insight you’ve gained about building products over the years, and how does building something today in 2026 compare to back in 2016?”
The biggest insight I’ve gained is that great products aren’t built just by following specifications, but by continuous adaptability and deep understanding of the end user. Back in 2016, building products was much slower. We focused heavily on manual setups, long execution cycles, and strict process steps. Today, with modern tools and AI acceleration, we can move from concept to execution at a much faster pace. The challenge has shifted from ‘how fast can we build things?’ to ‘are we building the right things?’
Q5: The View From Both Sides
“You’ve been on both sides of the table, as a developer writing the code, and as a Scrum Master guiding the team. What’s the one thing developers get completely wrong about what a Scrum Master actually does, and vice versa?”
From the developer side, most people often think a Scrum Master is just a ‘Jira administrator’ or someone who schedules meetings. But in reality, an SM is constantly working behind the scenes to shield the team from distractions and clear invisible blockers. In contrast, some Scrum Masters view developers as just ‘people who turn specifications into code.’ Having been a developer myself, I know that devs care deeply about why they are building something, not just how. When you treat developers as product thinkers rather than ticket executors, the whole team performs better.
Q6: When Process Gets in the Way of People
“Agile frameworks are designed to help teams move faster, but sometimes the process itself becomes the bottleneck. Has there been a moment where you had to throw the rulebook out and just do what actually worked? What did that teach you about the difference between following a system and truly leading one?”
Yes, absolutely. During high-pressure release cycles or urgent production issues, sticking strictly to standard ceremonies like daily stand up or long retrospectives can feel like an extra burden. In those moments, I’ve cancelled non-essential meetings and focused entirely on quick, direct syncs to let the team focus. What it taught me is that Agile is a tool to serve the team, not a set of rules to control them. If something isn’t working, we adapt and fix it based on the actual circumstances we face.
Q7: The Thing No Sprint Can Fix
“Sprint velocity, burndown charts, retrospectives, they’re all useful tools. But after years of running teams, what’s the one thing you’ve learned that no Agile framework or methodology can actually solve for you?”
Human trust and psychological safety. You can have the best Jira setup and strict sprint schedules, but if team members don’t feel safe to admit a mistake, ask for help, or challenge an idea, the framework won’t save you.
Q8: The Hard Lessons
“Some of the best lessons and insights come from things going sideways. Is there a specific moment where something went badly wrong, and what did you learn from picking up the pieces? How do you do that?”
Plenty of chaotic situations have happened, from misaligned requirements to production bugs caused by a wrong commit. The most important lesson we’ve learned from those moments is to avoid asking ‘who broke it,’ which only leads to finger-pointing. Instead, we focus on the why, where, when, and how so we can fix the system together.
Q9: The Slash Secret
“After all this time, what do you think genuinely sets Slash apart from every other tech company out there?”
To me, Slash is more than a company, it’s a diverse, living community. Many companies talk about culture, but we actually live it. There are no walls between clients, external members, developers, or management. We all wear the same Slash jersey, take ownership of the work, and support one another as one team.
Q10: The One-Liner
“Ten years in, summarized in a single sentence: What is Slash to you?”
Slash is a living community where everyone wears the same jersey.
