Build It Brigade
What Could Go Wrong Everything Thats the Point
The Unexpected Meeting
The Build It Brigade's shed smelled like sawdust, pencil shavings, and something Bea had spilled last week that she kept insisting was "just lemonade."
Cleo stood at the whiteboard, marker in hand, her yellow notebook open to a sketch that looked like a playground slide designed by someone who had never actually seen a slide.
"Perfect!" she announced. "The Waterfront Discovery Trail needs a viewing platform over the marsh. I'm thinking BIG. Like, balcony-level. Like, you can see the herons AND the otters AND-"
"Whoa, whoa, whoa." Rafi held up both hands. He was sitting on the workbench, which Dev had told him not to do approximately forty times. "Before we get to 'big,' can we talk about what could go wrong?"
Cleo waved her marker dismissively. "Nothing's going to go wrong. We've built bridges. We've built towers. We've built-"
"A bridge that sagged in the middle because we didn't calculate the live load properly. A tower that tipped over at 1:47 PM on a Tuesday because we forgot to account for wind. A water system that flooded the garden because the valve-"
"Okay, okay!" Cleo's cheeks went pink. "You don't have to list EVERYTHING."
Rafi pulled out his green notebook. "I have sixty-three entries."
"I know you have sixty-three entries. You bring it everywhere. You read it before bed."
"It's important to document failure," Rafi said quietly. "That's how we learn."
Bea looked up from the small wooden model she was already building without anyone asking her to. "Rafi's not wrong. The platform's going to be over MUD. Wet, squishy, not-holding-anything-up mud."
"Exactly!" Rafi jumped off the workbench. "The marsh edge is unstable. The soil composition changes seasonally. If we build a normal foundation, it'll shift within a year. Two years at most. And then the viewing platform becomes a viewing SLOPE."
Cleo opened her mouth, closed it, and sat down heavily on a stool. "When did you get to be such an expert on soil composition?"
"Book 15," Rafi said promptly. "Foundations: What's Under There. I read it three times. And then I read four more books from the library about soil mechanics. And then I checked the marsh's geological survey records from the town office."
There was a long silence.
Dev adjusted his glasses. "You checked the geological survey records?"
"They're public information." Rafi shrugged. "Told You So #61 was about the parking lot at the community center cracking exactly six months after it was resurfaced. The survey said the groundwater table was higher than the contractor thought. I wanted to know what else was in there."
Bea stopped sanding her model. "So... you've been checking things. For a while."
"Three years," Rafi said. "Since Book 8. The slippery hallway thing. That was Told You So #1."
Rafi Takes the Lead
Old Sal was stacking bags of cement mix in his hardware store when the Brigade arrived, practically vibrating with purpose.
"Ah," he said, not looking up. "You've discovered something."
"How did you know?" Cleo asked.
"Because Rafi has the look of a man who has been waiting for permission to talk about his favorite subject. And the rest of you have the look of people who just realized they should have been listening to him." Sal dusted off his hands. "What's the project?"
"A viewing platform over the marsh," Dev explained. "Rafi says we need to do something called 'safety engineering' before we design anything."
Sal's eyebrows went up. He walked slowly to the counter and leaned on it, which was his way of saying this conversation is going to be interesting.
"Safety engineering," he repeated. "That's a big phrase."
"It's not just about wearing helmets and checking that things are tight!" Rafi said, his voice faster than usual. "It's about looking at EVERYTHING that could go wrong before it goes wrong. Figuring out which failures are likely and which are rare. Deciding whether you can eliminate a hazard or just manage it."
Sal nodded slowly. "And you've been doing this informally for three years, haven't you?"
Rafi blinked. "I... yes? I didn't know it had a name. I just thought I was being annoying."
"You've been doing risk assessment," Sal said. "That's the engineering term. Looking at a design and asking: what are the ways this could fail? What would happen if it did? How likely is it? And then deciding what to do about it."
Cleo stared at Rafi as if seeing him for the first time. "So all those warnings about lateral loads and shear stress and-"
"Lateral load is real!" Rafi protested. "And shear stress is real! I wasn't making things up!"
"No, no, I know." Cleo shook her head slowly. "I just thought... well. I thought you read the manual because you were nervous."
"I read the manual because I wanted to know what could go wrong," Rafi said. "And then I wrote it down so I wouldn't forget."
Old Sal walked to the wall where the photograph of the collapsed bridge hung — the one he always used for teaching. "You know what that was?"
"A bridge that fell down," Bea said.
"A bridge that fell down because someone didn't do safety engineering." Sal tapped the photograph with one weathered finger. "They designed it beautifully. It was elegant. It was on budget. And it failed because nobody spent enough time asking what could go wrong. The bolts were the wrong grade for the load. The design accounted for weight but not wind. And the construction crew didn't follow the plan because they 'knew better.'"
He turned to face the Brigade. "Safety engineering isn't about being pessimistic. It's about being thorough. It's asking the question you don't want to ask, so you don't have to learn the answer the hard way."
Rafi stood a little taller.
"Rafi," Cleo said, "I think you should lead this project."
Dead silence.
"Me?" Rafi's voice cracked.
"You've been thinking about failure modes for three years without knowing the term." Cleo shrugged. "That IS the term. You're the expert. And I'm tired of being wrong about things when you told me so."
"She's offering you the lead," Dev said helpfully. "It's the Define stage. You're the one who knows how to define the problems."
The Failure Mode Party
Back in the shed, Rafi stood at the whiteboard for the first time. It felt strange. The marker felt heavy. He drew a wobbly square.
"This is the viewing platform," he said. "Now. How is it going to fail?"
"Someone falls off the edge," Bea said immediately.
"Good." Rafi wrote FALLING. "Someone falls through the railing."
"Someone falls through the railing because the railing breaks," Dev added.
"Good." CONNECTED FAILURE, he wrote. "The platform collapses entirely."
"Board cracks," Bea said.
"Platform sinks into the marsh."
"Wood rots."
"Rain makes the floor slippery."
"Wind blows someone's hat into the marsh and they lean too far trying to get it."
Rafi was writing fast now, his handwriting getting messier. "Good! GOOD! The wind catches the whole platform and twists it."
"People crowd on one side and it tips."
"Someone brings a really heavy piano up there for some reason."
Everyone turned to look at Cleo.
"What?" She held up her hands. "I said 'some reason.' I'm brainstorming!"
Rafi laughed, actually laughed. "The list is perfect. That's the thing. We can't predict every single possible failure — but we CAN predict the important ones. We look at each one and ask: how likely is it, and how bad would it be?"
He wrote two columns on the board. LIKELIHOOD and CONSEQUENCE.
"Getting your hat blown off is likely but not bad," he said. "The platform collapsing is low likelihood but catastrophic. The wood rotting over time is HIGH likelihood and HIGH consequence — so we eliminate it by using treated wood or composite decking. Falling off the edge is high consequence, so we eliminate it with railings that are higher than standard."
"What can't we eliminate?" Dev asked.
"People crowding on one side. Rain making the deck slippery." Rafi pointed at those items. "We can't stop people from standing where they want, and we can't stop rain. So we MANAGE those risks. We design the platform to hold more weight than any realistic crowd. We add grooves to the deck surface for grip. We put up a sign about conditions."
Bea picked up a pencil and started sketching. "So the railing has to be strong enough to stop a fall but not so strong it blocks the view."
"Exactly!" Rafi couldn't believe it. "You GET it."
"I always got it," Bea said. "I just didn't know the words for it."
Dev was scribbling calculations in his materials log. "The marsh soil is the real problem. If we build a normal foundation, it'll shift. We need something that spreads the load across a bigger area."
The Platform That Wouldn't Fall
Three days later, the Brigade stood at the edge of the marsh with a scale model of their design. It was beautiful — a wooden platform with sweeping railings, a grooved deck, and a foundation cleverly shaped like a wide paddle that spread the weight across the soft ground.
"It's not the fanciest design we've ever made," Cleo admitted. "But it's the most THOROUGH one."
"I think that's better than fancy." Bea crouched down and pushed gently on the model's railing. "It feels solid."
"This is the prototype phase," Rafi said. "We test it. But testing a model on dry ground isn't the same as testing it on marsh. So..."
He picked up the model and waded out into the muddy edge of the marsh, placed it carefully, and stepped back.
The model sat there. It didn't sink. It didn't tilt.
"Huh," Cleo said. "Is that it?"
"It doesn't LOOK like anything's happening," Dev said. "Is that a good thing?"
"It's the BEST thing." Rafi was grinning. "The whole point is that nothing happens. That's what safety engineering gets you. Boring success."
He waded back to the edge and pulled out his green notebook.
"What are you writing?" Bea asked.
Rafi flipped to a new page. At the top, he wrote: TOLD YOU SO #64. But then, underneath, he wrote: In which nothing went wrong, which is exactly what predictions were for.
"I'm documenting the success," he said. "Because knowing what could go wrong is only useful if you then actually go build the house — and come back later to make sure it's still standing."
Old Sal appeared on the path behind them, carrying a thermos of something that smelled like coffee. He looked at the model sitting peacefully in the marsh.
"Interesting," he said. "Nothing collapsed."
"That's the point," said all four kids at once.
Sal smiled. "Then you've learned this week's lesson." He nodded at Rafi. "That notebook of yours isn't a list of failures. It's a map of what to watch for. Every successful engineer has one, whether they write it in a notebook or just keep it in their head."
Rafi closed his green notebook and tucked it into his pocket. "I think I'm going to keep writing them."
"Do that." Sal took a sip from his thermos. "The difference between a pessimist and an engineer? A pessimist says 'what could go wrong' and gives up. An engineer says 'what could go wrong, and what are we going to do about it?'"
The four of them stood at the marsh's edge, looking at their small model platform sitting steady in the mud.
"I think," Cleo said, "this is the first time we've ever gone into the Build phase knowing exactly what we're doing."
"That's because we finally asked the right question," Bea said.
They all looked at Rafi, who was trying very hard not to look smug and failing.
"What?" he said. "I'm allowed to be right sometimes."
"Sixty-four times," Dev said.
And Rafi laughed, opened his notebook, and added: TOLD YOU SO #65: Team finally admitted I was useful.