Skip to main content
Module 3 Framework Your child has a validated concept. A College-Worthy Formula with five tight brackets. A Quick-Check Scorecard that says “go.” A 48-Hour Challenge that didn’t blow up in their face. Congratulations. Now watch what happens next. Because here’s the part nobody puts in the brochure: every student who has ever built a real has run face-first into at least two walls they didn’t see coming. Aiden’s first AquaGuard prototype leaked all over his garage floor. Raj’s initial FocusCraft design made attention worse, not better. Elena’s first batch of health guides had medical inaccuracies that a clinic nurse caught before they went out the door. Those aren’t cautionary tales. Those are success stories. The students behind them built work so undeniable it demanded attention. The difference between students who build real spikes and students who give up has nothing to do with talent, resources, or luck. It has everything to do with what happens after the plan meets reality. This chapter is about what goes wrong. The next one is about what to do when it does.
In this chapter:
  • The five most common traps that kill student projects before they ever generate real impact
  • Why your child will definitely fall into at least one of them — and why that’s fine
  • How each pitfall maps back to a specific step in the IMPACT Method — and how following the framework prevents them

​
The Five Project-Killing Pitfalls

Even with the behind them, students fall into the same traps over and over. We’ve watched it happen hundreds of times. Smart kids. Great ideas. Supportive families. And then… nothing. The project stalls, fizzles, or never quite launches. It’s almost always one of these five.

​
Pitfall #1: “Save the World” Syndrome

Your child comes home from their brainstorming session fired up. “I’m going to solve climate change!” Cool. What specifically? (Long pause.) ”…All of it?” And there’s your problem. Choosing massive, vague problems like “climate change” or “world hunger” with no specific angle isn’t ambition. It’s a poster in a dorm room. Because when the problem is everything, the solution is nothing. Where do you even start? Who are your beneficiaries? What does “solving climate change” look like for one high schooler with a laptop and 10 hours a week? It looks like a project that never gets off the ground. That’s what.
The vagueness trap:“I want to help the environment” is not a project. It’s a feeling. And feelings don’t generate evidence on the . The bigger and vaguer the problem, the smaller and vaguer the impact. Every time.
Remember Aiden from Chapter 2.4? He cared about the environment too. But he didn’t try to “save the ocean.” He zeroed in on microplastic pollution in storm drains in his specific coastal town. One pollutant. One delivery mechanism. One geography. That specificity is what made his project buildable, measurable, and — eventually — adoptable by three cities. The fix: focus on a specific sub-problem within the larger issue that your child can actually impact. Go back to Chapter 3.1’s Three Circles exercise. The problems worth solving aren’t the ones that make good bumper stickers. They’re the ones that are specific enough to do something about, verifiable enough to prove you did it, and meaningful enough to matter to real people. “Solve climate change” is a poster. “Reduce single-use plastic waste in my school’s cafeteria by 40% in one semester” is a project.
The specificity test from 3.1 still applies: Is the problem specific? Can you verify it exists? Is solving it meaningful? Can a high schooler realistically tackle it? If any answer is “not really,” zoom in further. The most impactful student projects aren’t the ones targeting the biggest problems. They’re the ones targeting the most specific problems.

​
Pitfall #2: The “Already Exists” Excuse

“But someone’s already doing that.” If we had a dollar for every time a promising project died because of this sentence, we could fund a few of those projects ourselves. Abandoning ideas because “someone’s already doing that” is one of the most common — and most wrong-headed — reasons students quit before they start. Here’s the thing: innovation rarely means inventing something entirely new. It often means improving existing solutions or applying them in new contexts. Uber didn’t invent taxis. Airbnb didn’t invent sleeping at someone’s house. Spotify didn’t invent listening to music. They took existing concepts and made them work better, for different people, in different ways. That’s not copying. That’s literally how innovation works. Your child doesn’t need to be the first person on earth to notice a problem. They need to be the person who solves it differently — for a specific community, using their specific advantages, in a way nobody else has tried. Remember the wallpaper advantage concept from Chapter 3.2? Lin’s family connections to textile manufacturers weren’t unique in any cosmic sense. Plenty of people know fabric manufacturers. But Lin combined that access with a design sensibility and a sustainability mission in a way that nobody else in her world was doing. The “already exists” test isn’t “has anyone ever done anything vaguely similar?” It’s “has anyone done it this way, for these people, with these advantages?” The answer is almost always no.
Reframe “it exists” as “I have a head start.” If someone else has tackled a similar problem, that’s not a stop sign — it’s free research. Study what they did. Find the gaps. Ask: who did they miss? What didn’t work? What’s changed since they tried? Your child’s project doesn’t need to be first. It needs to be better, or different, or more specific. That’s a much lower bar than inventing something from scratch — and it’s exactly how the real world works.

​
Pitfall #3: Permission Paralysis

This one’s sneaky. And it’s the one that gets the well-behaved kids. The rule-followers. The ones who’ve spent their entire academic lives raising their hands before speaking. Your child has a solid concept. They’ve run the formula. The scorecard looks good. And then… they wait. They wait for a teacher to approve it. They wait for an organization to invite them. They wait for some adult — any adult — to say “yes, you’re allowed to do this.” Nobody’s coming. Waiting for someone to authorize or validate your idea before starting is the silent killer of student projects. Not because the idea is bad — but because nobody is in the business of handing teenagers permission slips for projects they invented themselves. Adults are busy. Institutions are slow. And the window for building something meaningful before applications are due is not infinite.
The permission trap:Nobody is coming to give your child permission to start. No teacher. No counselor. No organization. The students who build real spikes don’t wait for an invitation. They start, build credibility through early results, and then approach gatekeepers with proof that their project works. That’s a fundamentally different conversation than “excuse me, may I please try something?”
Raj didn’t wait for a psychologist’s blessing to start building FocusCraft. He built a rough prototype, tested it with his cousin, got interesting results, and then approached a psychologist to partner on a formal study. By the time he was asking for help, he already had something to show. That’s not disrespectful. That’s entrepreneurial. And it’s exactly the kind of initiative that made Stanford pay attention. The fix: start small and build credibility through results, not by seeking pre-approval. The 48-Hour Challenge from Chapter 3.3? That’s your child’s permission slip. A working prototype and three beneficiary interviews give them more credibility than any approval letter ever could.
The “forgiveness over permission” approach (within reason): Your child doesn’t need permission to record a tutorial video, interview community members, create a resource guide, or build a prototype in their bedroom. They need permission when they’re asking to use someone else’s space, resources, or name. For everything else? Start. Build. Show results. Then ask for partnership — not permission.

​
Pitfall #4: The “Perfect Project” Myth

This is the one that gets the overachievers. The straight-A students. The kids who’ve spent their entire academic career turning in polished work, never submitting anything less than excellent. Those habits that got them a 4.0? They’ll kill their spike. Because spike-building isn’t school. There’s no rubric. There’s no grading curve. There’s no teacher who’ll give them a B+ for a really good effort. And endlessly refining ideas without ever executing them is the fastest route to a beautifully planned project that never becomes a real one. We’ve seen students spend months perfecting a project proposal. Revising their College-Worthy Formula seventeen times. Designing a logo before they’ve talked to a single beneficiary. Color-coding a Gantt chart for a project that doesn’t exist yet. Meanwhile, the student who started with a janky prototype and a Google Doc has already run three iterations, collected real data, and is climbing the Evidence Pyramid while the perfectionist is still picking fonts.
Perfectionism is procrastination in a lab coat.It feels productive. Your child looks busy. They’re “working on the project.” But if the project hasn’t touched a single beneficiary after month one, the planning has become the project — and that’s a problem. The Evidence Pyramid doesn’t have a level for “beautifully planned but never launched.”
The fix: embrace “good enough to start” and improve through iteration. Remember Chapter 3.3’s startup principle? Ship something small, learn fast, iterate. Noah’s first video was shot on his phone with a whiteboard. No editing. No graphics. It looked terrible. And it was the video that proved his concept worked. If he’d waited until the production quality was YouTube-worthy, he’d still be waiting.
The 80% rule: If your child’s prototype is 80% ready, it’s ready. The last 20% of polish almost never changes whether the concept works or not. Ship it. Test it. Get feedback. Then use that feedback to make version 2 better than version 1 could ever have been on its own. Iteration beats perfection. Every single time.

​
Pitfall #5: The “Passion Only” Trap

This one’s tricky because it sounds like good advice. “Follow your passion!” “Do what you love!” “The project should come from the heart!” Sounds great on a motivational Instagram post. Terrible advice for building a spike. Choosing projects based solely on interest without considering impact potential is how you end up with a hobby, not a spike. A student who’s passionate about photography and starts a photography Instagram has a hobby. A student who’s passionate about photography and documents the demolition of historic buildings in their neighborhood to create an archive that the city planning commission uses? That’s a spike. Same passion. Different planet. The difference is the second student ran their interest through the Venn Diagram from Chapter 3.2 and found the intersection where passion meets problem meets advantage. The first student skipped Steps M, P, and A and jumped straight to “I like taking pictures.” The fix: use the IMPACT framework to find the sweet spot where passion meets meaningful problem-solving. We built an entire chapter (3.2) around this exact intersection. If your child’s project concept lives in only one circle of the Venn Diagram — if it’s all passion and no problem, or all problem and no advantage — the concept isn’t ready. Go back. Find the overlap. That’s where spikes live.
All five pitfalls share one root cause: skipping the framework. “Save the World” skips the specificity filter from 3.1. “Already Exists” skips the advantage analysis from 3.2. Permission Paralysis skips the 48-Hour Challenge from 3.3. The Perfect Project Myth skips the MVP mindset from 3.3. And the Passion Only Trap skips the Venn Diagram from 3.2. The IMPACT Method exists precisely to prevent these traps. If your child follows the steps, these pitfalls become nearly impossible to fall into. If they skip the steps? Nearly impossible to avoid.

​
The Traps Are Mapped. Now What?

Here’s the good news: you now know what’s coming. And knowing what’s coming is most of the battle. Most families walk into the spike-building process blind. They don’t know about Permission Paralysis until their kid has been “waiting to hear back” for three months. They don’t recognize the Perfect Project Myth until the Gantt chart has its own Gantt chart. They don’t see Save the World Syndrome until the project proposal reads like a UN resolution. You’ve just read the scouting report. You know the five traps. You know which IMPACT steps prevent each one. You know what to watch for. But here’s the part that makes this harder than it sounds: even with the framework, even with the scouting report, things will still go sideways. Not because your child did anything wrong. Because that’s how building things works. The prototype leaks. The beneficiaries ghost. The concept that scored a 38 on the scorecard in Month 1 is scoring a 25 by Month 3. When that happens — and it will — the question isn’t “what went wrong?” It’s “what do we do now?” That’s the next chapter.
Your Assignment: Know Your VulnerabilityBefore your child’s project hits its first wall (and it will), sit down together and do this:
  1. Review the five pitfalls together. Read through all five with your child. Which one is most likely to trip them up? The perfectionist? The “save the world” dreamer? The one who’ll wait for permission? Knowing your vulnerability is half the defense.
  2. Identify the framework step that prevents it. For whichever pitfall your child is most susceptible to, go back to the specific IMPACT step that guards against it. Reread that section. Make sure the exercise was completed thoroughly — not just skimmed. The framework only works if it’s actually used.
  3. Create a “pitfall check-in” habit. Every two weeks, ask: “Are we falling into any of the five traps?” Make it casual. Make it quick. But make it regular. The traps are easiest to escape when they’re caught early. By Month 3, they’ve become habits.
Coming up next: You know the traps. But what do you do when things go wrong despite avoiding them? In Pivots, Setbacks, and Getting Unstuck, we tackle the hardest decision in spike-building — when to pivot versus when to push through — and the most counterintuitive lesson of all: how failures and setbacks actually strengthen a college application. Plus, your Module 3 recap and the bridge to Module 4.