Shape Up: Stop Running in Circles and Ship Work that Matters

Hey there, fellow public servants. You know that feeling, right? Yeah. Of just constantly like swimming upstream, limited resources, tons of competing priorities, and always that pressure to deliver, you know, meaningful results for our communities. For sure, for sure. So today we're diving into a method that might just be the life raft we need. Ooh, I like that. ShapeUp. Okay. Have you heard of this? I have heard of ShapeUp, yeah. It's a project management approach developed by the software company Basecamp. Oh, yeah. And what's really fascinating is how it flips the script on traditional project planning. Instead of starting with scope and then trying to cram it into a time frame, ShapeUp focuses on a fixed time budget first. Yeah, okay. So it's kind of like saying, all right, we have six weeks. Yeah. What is the most impactful thing we can achieve in that time? Exactly. It almost sounds radical, right? It can be a little bit radical, but I think it's a good radical. Yeah. It's like the right amount of radical. Right. Because think about how often in public service, especially, projects get bogged down by scope creep-blown deadlines. Yes. And just, you know. It never ends. Yeah. It never ends. And this fixed time variable scope concept is really like that bedrock foundation. Right. Of ShapeUp. And it... forces you to make those tough choices up front. Yeah. And really prioritize what matters. Totally. So let's unpack this a little bit. Okay, let's do it. And let's start with this idea of shaping work. Yeah. Before we dive into building. Okay, so imagine you're tasked with, like, okay, improve citizen engagement. Oh, yeah, big one. Huge goal, right? Absolutely. Where do you even begin? So many places to start. So many places, so many rabbit holes. Right. Instead of jumping into solutions like shape up. encourages you to really like zoom in on the problem. Yes. Define it with like laser focus. Right. What specifically is hindering engagement? Is it lack of awareness of services? Is it difficulty accessing information? Is it something else entirely? Yeah. Like equally important. Yeah. How much time and resources? What they call appetite. Okay. Appetite. Are you realistically able to dedicate to this? I like that appetite. Yeah. Because I can already hear some of our listeners being like, oh yeah. But we're public servants. Yeah. We always want to serve. Our appetite is endless. Yes. Our appetite for serving is definitely endless. But realistically, we do have to work within some constraints. For sure. Right. Absolutely. And that's where appetite becomes like this really powerful tool. Okay. It's about aligning leadership stakeholders and teams. Right. Around this shared understanding of what is achievable. You might want to revamp the entire citizen portal. Oh, yeah. But if your appetite only allows for six weeks. Right. You need to shape a solution. That fits within those constraints. I love how this challenges us to think differently. Yeah. It's about being strategic. It's about delivering value, even with limited resources. Right. Which is often the case. Always. Always. In the public sector. And it helps avoid those rabbit holes. Yes. That can just plague public service projects. Oh, for sure. Like, you know that feeling when you start with this, like, clear goal? Right. And then like six months later, you're just lost in this maze of committees and revisions. And you're like, what happened to my initial vision? I know. I know. And it happens. I think all the time. All the time. All the time. So the source material actually has this great example. Oh, yeah. Of how Basecamp. use this shaping process to create something really valuable in a short time frame. Yeah, I'm curious. The dot grid calendar. The dot grid calendar. They were getting just bombarded with requests for this full-blown calendar future. Oh, wow. Yeah. Which could have easily turned into this six-month behemoth. Which in the world of public service, six months can sometimes feel like a decade. Yeah, sometimes it does, especially when you're dealing with, you know. Right. Constantly shifting priorities. Right. Limited budgets. Limited budgets. Absolutely. So instead of trying to cram a six-month project into like six weeks. Right. They took a step back and I said, okay, what is the core need here? And what they discovered was that a lot of users just needed a simple way to visualize. Oh, interesting. Free spaces. Right. on a calendar right just like when am i free yeah i don't need to know all the details exactly and that shift yeah in perspective i think is key yeah because it allowed them to define a scope yeah that was both achievable and valuable right within their fixed time budget perfect and the results yeah what was it the dot grid calendar okay simple user-friendly solution yeah that they were able to develop in just six weeks wow I think that's a really powerful lesson for us in public service. I think so, too. You know, we don't always need these complex, time-consuming solutions. Totally. Sometimes a well-shaped, focused approach can deliver a much bigger impact in a fraction of the time. For sure. For sure. And that leads us to another key aspect of shape-up. Okay. I'm excited. Which I think resonates deeply with the public sector. Okay. Targeted risk reduction. I like this. Okay, think about all the times a project has gone off the rails. I don't want to think about it. Because of unforeseen problems. It's painful. Don't get me started, right? Right. It's like every project comes with its own Pandora's box of surprises. Yeah. A critical vendor backs out a new regulation. Oh. Throws a wrench in your plans. Uh-huh. Or the public feedback reveals a major flaw in your design. Oh, no. Can be incredibly frustrating. The worst. And that. is where shape up gets really interesting okay tell me more because instead of just hoping for the best and dealing with problems as they arise the classic it emphasizes actively identifying yes and addressing risks before work even begins so it's about being proactive so by being proactive not reactive i love that and that's something i think we could all benefit from in public service a hundred percent so they give this example okay from their own work The To Do Groups project. The To Do Groups project. And before handing it off to the development team. Okay. They realized there was a potential issue with displaying completed items. Interesting. It wasn't like a deal breaker. Okay. But it was something that could easily have caused delays and frustration later on. Down the line. So what did they do? Did they halt the project? Go back to the drawing board? That's what's so smart about this approach. They didn't try to come up with the most elegant solution right then and there. They made a conscious decision to simplify that aspect of the project, focusing on mitigating the risk and keeping that core functionality on track. So they essentially said, we're not going to let this one potential issue derail the entire project. We'll address it in a way that keeps us moving forward. Exactly. It's about making strategic choices. And accepting that not everything needs to be perfect on the first try. Right. Which I think is a really important lesson for us in public service. Oh, for sure. Yeah. We're often so focused on getting things right. Right. That we can get paralyzed. Yes. By perfectionism. A hundred percent. But sometimes. Yeah. A good enough solution. Yes. Delivered on time. Uh-huh. Is much more valuable than a perfect solution that never sees the light of day. Could not agree more. Right. Yes. And this kind of brings us to another principle that I think really resonates with public servants empowering teams and honoring commitments. Hmm. Honoring commitments. Yeah, we talk a lot about, you know, empowering frontline workers and fostering this culture of innovation and public service. Right. But, you know, how often do we actually give teams the autonomy to really make decisions and solve problems without all those layers of bureaucracy and approvals? That's a great point. Yeah, and it's where ShapeUp takes a very different approach. Okay. It emphasizes handing off entire projects to teams. Whole projects. Giving them that ownership and that freedom to really figure out. Wow. How to best achieve the desired outcome. So instead of handing down this list of predefined tasks and like micromanaging every step of the way. Right. We're trusting our teams to be the experts. Yes. And giving them the space to do what they do best. 100%. It's about setting those clear boundaries like the scope and the time frame. Right. And then really letting the team run with it. Okay. So. This might sound a little unsettling to some managers out there who are used to having a tight grip on the reins. That's for sure, yeah. But I think it's a crucial shift in mindset if we want to truly empower our teams and unleash their creativity. Absolutely. I agree. And this leads us to one of the most intriguing and maybe controversial aspects of ShapeUp. Ooh. The circuit breaker. The circuit breaker. Yeah, have you heard of this? I have. And I'll admit, the first time I read about this, I thought it was a little harsh. Okay. Tell me why. It's this idea that if a team doesn't finish a project, within that fixed time frame, the default response is not to extend the deadline. You're not alone in feeling that way. Really? It goes against everything we've been conditioned to believe about project management. I know. But think about it. How often does extending a deadline actually lead to a better outcome? You know, in my experience, not very often. Right. Usually it just leads to more stress, more scrambling, and just a lower quality product in the end. Exactly. It's like putting a Band-Aid on a broken bone. Ooh. You know, it might cover up the problem temporarily. Right. But it doesn't actually address the root cause. So the circuit breaker. Yeah. It forces a different kind of conversation. It does. If a team isn't going to meet the deadline, they have to hit the circuit breaker and reassess. And this can be incredibly valuable. How so? Because it might mean reshaping the project, prioritizing different aspects, or even making the tough decision to pull the plug altogether. It's about acknowledging that sometimes, even with the best intentions and the best effort, things don't always go according to Cologne. And it's better to make a strategic course correction than to keep pushing towards a deadline that's just no longer realistic. A hundred percent. And this principle of honoring commitments... It goes beyond internal deadlines, too. It's about being accountable to the public. Oh, interesting. And delivering on the promises that we make. Oh, for sure. So think about, you know, a project to improve access to social services. Okay. If we're missing deadlines and keep pushing back the launch date, it's not just an inconvenience. Right. It's a real impact on people's lives. That's a great point. Yeah. And the circuit breaker mindset can really help us make those tough decisions. Right. In a way that prioritizes both the needs of the project and the needs of the people we serve. Okay. So let's talk about something that is just a constant struggle. Yeah. In public service, communicating progress effectively. Yeah. So we're often asked, what's the status of this project? Yep. And it can feel like we're stuck between these two extremes. Totally. On the one hand, you have those detailed task lists and gaunt charts. Yes. That try to map out every single step. Oh. But they're often outdated the minute they're created. And then on the other hand, you have these vague pronouncements of it's in progress or we're working on it. Yep. Which don't really give anyone a clear understanding of where things stand. No. And this is where Shape Up offers a very refreshing alternative, the Hill Chart. The Hill Chart. You know, when I first read about the Hill Chart, I was a little skeptical. Okay. It seemed... almost too simple. Yeah, I hear that. But the more I thought about it, the more I realized it's brilliance. Okay, tell me more. It's a visual metaphor that everyone can understand, regardless of their technical expertise. I love that. So instead of getting bogged down in these granular tasks or those dreaded percentage estimates, that never seemed to reflect reality. The Hill chart uses the simple visual to communicate progress. So how does it work? Okay, so imagine a hill. Okay, a hill. I got it. At the beginning of a project, you're climbing uphill. Okay. There are a lot of unknowns. Yeah. You're exploring different paths. You're making discoveries along the way. Right. Then as the team starts making progress and solving problems, they begin to crest the hill. They're getting there. They can see the path forward more clearly, and the finish line is in sight. They can see the top. Exactly. And finally, as they wrap up the remaining tasks and kind of polish that final product, they're coasting downhill toward completion. Oh, I love that visual. It's such a powerful visual because it captures that natural flow of a project. And it communicates progress in a way that I think everyone can grasp intuitively. 100%. And what I love about it is that it allows managers to provide support without micromanaging. Okay. How so? They can glance at the Hill chart and immediately see where things are getting stuck or where a team might need additional resources. Right. They can get a sense of where things are at. Exactly. It fosters this culture of trust and transparency, which I think is so important in public service. Absolutely. I agree. Now, you mentioned earlier that shape-up has some elements that might feel a little controversial. Yeah. Especially in the context of public service. Right. And one of those is the way they approach bugs. bugs the bane of our existence. Right. In a world where we're constantly striving for, like, error-free service delivery. Right. The idea of not prioritizing every bug might seem a little counterintuitive. I can already hear the gasps. Oh, yeah. From our listeners. Totally. But before everyone panics. Yes. Let's unpack this a little bit. All right, let's do it. ShapeUp doesn't advocate for ignoring bugs altogether. No, of course not. Of course, if there's a major system outage or a critical security vulnerability, you address it immediately. Right away. But the vast majority of bugs aren't showstoppers. They're annoyances, inconsistencies, or these minor glitches that, while not ideal, don't prevent the core functionality from working. And what ShapeUp suggests is that we shift our mindset from reactive bug fixing to more strategic bug management. Oh, interesting. So instead of interrupting the flow of a six week cycle every time a bug pops up. Right. They advocate for using those cool down periods between cycles. OK. To address bugs in a more dedicated way. So it's not about ignoring them. Right. It's about being more intentional and strategic about when and how we are them. Exactly. I love that. And this frees up teams to focus on delivering new value during those crucial six-week cycles. Right. Which ultimately, I think, leads to a better overall experience for the public. I agree. It's about recognizing that sometimes fixing every tiny bug can actually hinder our ability to deliver meaningful progress. Right. So it's about picking your battles. It is now another challenge. Oh, there's more. There always is. There's more challenges. That, I think, resonates with... everyone in public service is this like constant influx of new ideas, requests and feedback that can derail even the most well-planned project. Absolutely. It's like we're constantly being bombarded. Yes. From all sides. Can you just add this one feature or we need to address this urgent issue right now? Right. It's overwhelming and it's easy to get pulled in a million different directions. Totally. And ShapeUp offers this deceptively simple but incredibly powerful solution. They don't. They just ignore all that feedback? Not exactly. They advocate for what they call letting the storm pass. Letting the storm pass. Yeah. So instead of reacting immediately to every new idea or a new request, they suggest taking a step back, letting the dust settle, and then evaluating those ideas strategically. So instead of getting swept away by every... wave of new ideas, we're creating a space for thoughtful consideration. Exactly. And here's the best part. All that feedback, all those new ideas, they don't just disappear into a black hole. They become fuel for the next round of shaping, you know, so we can take all those insights, those pain points, those suggestions and use them to shape even better projects in the future. It's a continuous cycle of learning and improvement. I like that a lot. Yeah. It resonates a lot with like the idea of being responsive to the needs of our community. Right. You know, we're not just like shutting down input. Yeah. We're creating a structured way to gather it and prioritize. For sure. For sure. You know, if we step back and look at the core principles of shape up. Okay. Like shaping before building, targeting risk reduction, empowering teams, communicating progress effectively. Yeah. It's really about moving away from that reactive, always on firefighting mode. Oh, yeah. That's so prevalent in public service. All the time. Yeah. Right. It's about embracing a more deliberate, strategic, and ultimately more impactful way of working. I like that. Yeah. And it's about shifting our mindset, you know, from how do we get all this done to what's the most valuable thing we can achieve with the time and resources we have. 100%. And I think that shift is really crucial if we want to truly make a difference in the lives of the citizens we serve. So as we wrap up this Deep Doss, I want to leave you with a challenge. Ooh, a challenge. I like it. Think about that problem. Yeah. That keeps you up at night. That initiative that's been stuck in the planning phase. Yep. for far too long or that service that just isn't meeting the needs of your community. What if you applied this shape-up mindset to that challenge? Imagine setting a fixed time frame, defining a clear scope. empowering your team and communicating progress in a way that everyone understands. The powerful stuff. It might feel like a radical departure from the way things are usually done, but the potential rewards I think are enormous. They are. That opportunity to deliver real value to your community, to boost team morale, and to reclaim a sense of control over your work. Yes, to all of that. So go out there, fellow public servants. Yeah. And shape up some truly impactful work. I love it.

Source: https://basecamp.com/shapeup

In this episode, we explore Ryan Singer's methodology for product development at Basecamp. Shape Up offers a refreshing alternative to traditional agile practices, focusing on six-week cycles, clearly shaped work, and autonomous team responsibility. The book outlines a three-part process: Shaping (defining project boundaries and solutions before committing resources), Betting (making deliberate decisions about what to work on instead of maintaining endless backlogs), and Building (giving teams full responsibility to execute projects with practical techniques for showing progress and making scope trade-offs). Learn how to break free from endless meetings, unclear requirements, and missed deadlines to create a more focused, effective product development process.

The contents and hosts of this podcast are AI generated.