Tag: Paul Graham

  • Rethinking University Founder Education: Beyond Business Plans to Real-World Building

    Rethinking University Founder Education: Beyond Business Plans to Real-World Building

    Rethinking Entrepreneurship in Higher Education: 7 Ways Universities Must Evolve Now to Meet the Change

    When Paul Graham, co-founder of Y Combinator, wrote an essay on how universities should prepare founders, it sparked a debate that cuts to the heart of modern higher education. The traditional entrepreneurship course where students write business plans and pitch to mock investors does little to create the resilience, technical skill, and customer obsession that define successful startup founders. Graham’s argument is simple: if universities want to produce founders, they must shift from teaching about entrepreneurship to enabling actual building.

    The Problem with Traditional Entrepreneurship Education

    Most university entrepreneurship programs are housed in business schools, focusing on writing business plans, financial modeling, and management theory. These skills are useful for running a company, but they are not the core of founding one. A founder’s primary job is to create something people want, a process that involves rapid iteration, direct customer feedback, and technical execution none of which can be learned from a case study.

    Consider the typical capstone project: students form teams, write a 50-page plan, and present to a panel of judges. In the real world, the plan is obsolete the moment it meets a customer. The lean startup methodology, popularized by Eric Ries, emphasizes building a minimum viable product (MVP) and testing it with real users. Universities that cling to the old model are teaching students to be corporate managers, not founders.

    The Y Combinator Model: Learning by Doing

    Graham’s perspective is shaped by Y Combinator, the accelerator that has funded over 3,000 startups, including Airbnb, Dropbox, and Stripe. YC’s approach is stark: founders apply with an idea, get accepted into a cohort, and spend three months building their product with weekly office hours from seasoned mentors. The focus is entirely on making something people want, not on writing plans. Demo Day, where founders pitch to investors, is the culmination—but the real education happens in the daily grind of building.

    Universities can adapt this model. Instead of a semester-long business plan, imagine a course where students must launch a real product to real users. They would need to code, design, market, and iterate—all with the safety net of university resources. The grading would be based on traction (users, revenue, engagement) rather than a paper. This is not a hypothetical; some universities already do this. Stanford’s d.school offers project-based courses, and MIT’s Sandbox program funds student startups. But these are often extracurricular, not integrated into the core curriculum.

    Identifying Founder Traits: Selection Over Instruction

    One of Graham’s most provocative suggestions is that universities should focus on identifying students with founder potential, rather than trying to teach everyone to be a founder. This is a selection problem, not an education problem. Successful founders tend to share traits: a bias toward action, comfort with ambiguity, resilience in the face of rejection, and a deep understanding of a specific problem. Universities can spot these traits through student projects, competitions, and even psychological assessments.

    YC itself is a selection machine. It receives thousands of applications for each cohort and accepts less than 2%. The interview process is intense, focusing on the founders’ determination and clarity, not just the idea. Universities could do the same: create competitive programs that require students to demonstrate their skills before gaining access to resources. This would be a radical departure from the open-enrollment model, but it would align incentives—students would work harder to earn a spot, and the program would attract the most driven individuals.

    Normalizing Failure: The Missing Lesson

    A major obstacle to founder education is the stigma around failure. In universities, failure is punished with bad grades and shame. In the startup world, failure is a stepping stone—most successful founders have failed multiple times before hitting their stride. A university that wants to prepare founders must create a culture where failure is not just tolerated but celebrated as a learning opportunity.

    One way is to grade students on the process, not the outcome. If a student launches a product that gets no users, they can still earn top marks by documenting what they learned and how they pivoted. This is the opposite of the perfectionist culture in academia, where a B+ can feel like a catastrophe. By reframing failure as data, universities can help students build the resilience they need to survive the startup grind.

    The Role of Networks: Connecting Students to Real Founders

    Another key component is exposure to working founders. Most university entrepreneurship courses are taught by professors who have never started a company. They can teach theory, but they cannot convey the visceral experience of pitching to a skeptical investor or the loneliness of a 3 a.m. debugging session. Bringing in guest speakers is not enough; students need ongoing mentorship from people who have been in the trenches.

    Universities are uniquely positioned to facilitate this. They have alumni networks full of founders, investors, and operators. A structured mentorship program, where each student founder is paired with a successful alumnus, could provide the guidance that no textbook can offer. Moreover, connecting students with local startups for internships or project collaborations can give them a taste of the real world while still in school.

    The Skeptical View: Should Universities Even Do This?

    Not everyone agrees. Critics argue that universities’ core mission is education, not startup creation. Funding founder programs could divert resources from humanities and basic science. Furthermore, the high failure rate of startups means many students will not succeed, potentially wasting their time and tuition money. There is also a question of elitism: YC-backed founders are a tiny, privileged fraction; should public universities allocate scarce resources to groom a few potential billionaires?

    These are valid concerns, but they miss a larger point. Founder skills—like resilience, creativity, and problem-solving—are valuable in any career, not just startups. Even if a student never starts a company, learning to build a product and empathize with users will make them a better employee, researcher, or civil servant. Moreover, universities already invest in career services, which prepare students for the corporate ladder. Offering an alternative path for those who want to build something new is a natural extension.

    A Path Forward: Practical Recommendations

    For universities willing to embrace this challenge, here are concrete steps:

    1. Create a founder track within existing majors, not a separate program. Students in engineering, computer science, or even liberal arts should be able to replace a traditional capstone with a startup project.
    2. Fund micro-grants for student experiments. YC gives each startup $500k; universities can give $5k to cover hosting, software, or user testing. The key is to remove financial barriers.
    3. Establish a “founder-in-residence” program. Bring in a successful founder to spend a semester on campus, mentoring students and teaching a hands-on course.
    4. Develop a network of local startups willing to host student interns for credit. This provides real-world experience without the risk of a full-time commitment.
    5. Change the grading rubric for project courses. Emphasize iteration, user feedback, and learning, not just the final product.

    These steps are not radical; they are incremental. But they signal to students that the university values action over theory, and that is the first step toward creating a founder culture.

    Conclusion

    Universities have a choice: continue churning out employees or start preparing founders. The demand is there—students increasingly want to create their own paths. By embracing the principles of learning by doing, selecting for founder traits, normalizing failure, and connecting students with real-world mentors, universities can fulfill a new mission. The future belongs to those who build, and universities can be the launchpad.

    The debate sparked by Paul Graham’s essay is not just about entrepreneurship education; it’s about the purpose of a university in the 21st century. As the cost of starting a company drops and the tools for creation become accessible, the ability to build and launch products is a fundamental skill. Universities that adapt will produce graduates who are not just job-ready but world-ready—ready to shape the future, not just fit into it.

    Summary

    • Traditional entrepreneurship education focuses on business plans, but founders need to build and iterate.
    • The Y Combinator model emphasizes learning by doing, with a focus on making something people want.
    • Universities should select for founder traits rather than trying to teach everyone to be a founder.
    • Normalizing failure is essential; students need to learn from setbacks, not fear them.
    • Connecting students with real founders and local startups provides mentorship that theory cannot.

    FAQ

    Q: Is entrepreneurship education the same as founder preparation?
    A: No. Entrepreneurship education often covers management, finance, and business planning. Founder preparation focuses on the specific skills needed to start a company, like building a product, getting users, and iterating.

    Q: Can universities really teach resilience and a bias toward action?
    A: These traits are more about selection and environment than instruction. Universities can create programs that reward risk-taking and persistence, and select students who already exhibit these qualities.

    Q: What about the risk of students failing and wasting resources?
    A: Failure is a learning opportunity. Universities can change grading to reward the process, not just the outcome, so students gain value even if their startup does not succeed.

    Q: How can universities without huge budgets implement these ideas?
    A: They can start small—partnering with local startups, inviting guest speakers, and offering courses that replace traditional projects with hands-on building. Even modest changes can shift the culture.

    Q: Is it fair to focus resources on a few potential founders?
    A: Founder skills benefit many careers, not just startups. And by creating competitive programs, universities can ensure they are investing in the most motivated students, which is a fair use of resources.

  • How to Do Great Work: A Practical Guide from Paul Graham

    How to Do Great Work: A Practical Guide from Paul Graham

    In July 2023, Paul Graham—co-founder of Y Combinator and one of the most influential voices in tech—published an essay simply titled ‘How to Do Great Work.’ It quickly became a touchstone for anyone striving to create something meaningful, whether in science, art, or entrepreneurship. But what does ‘great work’ actually mean, and how can you achieve it? Graham’s answer is not a secret formula or a stroke of genius; it’s a deliberate, iterative process that anyone can adopt.

    This article unpacks Graham’s core ideas, translating them into actionable steps. You’ll learn how to choose the right problems, develop a ‘taste’ for quality, and cultivate the resilience needed to see long projects through. Whether you’re a student, a founder, or a creative, these principles offer a roadmap for turning curiosity into impact.

    The Core Idea: Great Work Is a Process, Not a Gift

    Paul Graham’s central thesis is that great work—work that is novel, useful, and impactful—is not the result of raw talent alone. Instead, it emerges from a deliberate, iterative process. He emphasizes that you can’t just wait for inspiration; you have to actively seek out problems, learn the landscape, and then chip away at them with relentless effort.

    Think of it like a sculptor. A block of marble doesn’t become a statue by itself; the sculptor must study the stone, find the shape within, and then work with tools to reveal it. Similarly, great work is revealed through a process of exploration and refinement. Graham’s essay is essentially a guide to becoming that sculptor of your own ideas.

    Step 1: Decide What to Work On

    The first and most crucial step is choosing your problem. Graham advises that you should work on something that interests you deeply and seems important. He calls this ‘ambitious curiosity’—a combination of genuine fascination and a desire to make a difference.

    But how do you find such a problem? Graham suggests you start by asking yourself what you’re curious about, what puzzles you, and what you find yourself thinking about when you’re not forced to. It’s not about picking the ‘hot’ topic or the one that will make you famous; it’s about following your own intellectual passions.

    For example, if you’re a computer science student, don’t just pick a thesis topic because it’s trendy. Instead, think about the problems that make you lose track of time. Maybe it’s how to make algorithms more efficient, or how to build software that’s easier for people to use. That genuine interest will sustain you through the hard work ahead.

    Step 2: Learn Enough to Get to the Frontier

    Once you’ve chosen your area, you need to master what’s already known. Graham calls this ‘getting to the frontier’—the edge of human knowledge in your field. This means reading papers, studying the work of others, and understanding the current state of the art.

    But don’t stop there. The frontier is where you’ll find the ‘interesting anomalies’—the things that don’t quite fit, the contradictions, the unexplored niches. These are the cracks where great work often emerges.

    Imagine you’re a historian studying a well-documented period. You read all the major texts, but you notice a minor event that doesn’t align with the standard narrative. That anomaly is your crack. It’s a chance to ask a new question and potentially uncover something significant.

    Step 3: Look for ‘Cracks’ or ‘Seams’

    Graham uses the metaphor of ‘cracks’ or ‘seams’ to describe the opportunities for great work. These are the overlooked details, the contradictions, and the unexplored areas that others have missed. Finding them requires a combination of deep knowledge and a fresh perspective.

    One way to spot cracks is to question assumptions. Ask yourself: Why is this the accepted view? What if it’s wrong? What if we looked at it from a different angle? This kind of thinking can lead to breakthroughs.

    For instance, in the early days of the internet, many people assumed that online commerce would never work because people wouldn’t trust it. But a few entrepreneurs saw a crack: the possibility of building trust through reviews and secure payments. That insight led to companies like Amazon and eBay.

    Step 4: Work on Projects, Not Just Skills

    It’s tempting to focus on building skills—learning a programming language, mastering a technique, or reading more books. But Graham argues that skills are only useful when applied to projects. Projects force you to produce tangible output, which is where the real learning and iteration happen.

    A project is a specific, finite goal: write a paper, build a prototype, compose a piece of music. It has a beginning and an end, and it produces something you can show to others. This is different from just ‘practicing’ or ‘studying’.

    For example, if you want to become a better writer, you could read books on writing (skill-building), but you’ll improve much faster by writing a blog post or a short story (project). The project gives you a concrete outcome to evaluate and refine.

    Step 5: Iterate and Refine

    Graham is clear that your first attempts will likely be flawed. That’s okay. The key is to keep improving, to work on things that ‘seem like they might be good’ and then refine them based on feedback and your own judgment.

    This is the iterative process: create a rough draft, get feedback, revise, repeat. It’s how great art, great science, and great products are made. The first version of Google was not the polished search engine we know today; it was a rough prototype that was constantly refined.

    Don’t be afraid of imperfection. Instead, embrace it as a starting point. The goal is not to get it right the first time, but to get it better each time.

    Step 6: Cultivate a ‘Taste’ for Quality

    To know what ‘good’ looks like, you need to develop a sense of taste. This is an aesthetic judgment that guides your choices. In science, it’s knowing what a beautiful theory looks like; in art, it’s knowing what a powerful composition feels like; in business, it’s knowing what a compelling product is.

    How do you develop taste? By exposing yourself to the best work in your field and by constantly asking yourself what makes it good. Over time, you’ll internalize these standards and use them to evaluate your own work.

    For example, a young filmmaker might watch dozens of classic movies, analyzing why they work. That analysis builds a sense of taste that will inform their own directing choices.

    Step 7: Embrace ‘Slow Hunches’

    Great ideas often don’t come in a flash of insight. Instead, they develop over years as ‘slow hunches’—half-formed thoughts that you keep in the back of your mind and revisit over time. Graham advises keeping a notebook of these ideas, so you don’t lose them.

    This is why many great thinkers are known for carrying notebooks. They jot down observations, questions, and snippets of ideas, and then later, they connect the dots. The hunch that seemed trivial at first might become the seed of a major project.

    For instance, Charles Darwin’s theory of natural selection didn’t emerge fully formed. It was the result of years of collecting observations and slowly developing the idea, which he finally articulated in ‘On the Origin of Species.’

    Step 8: Collaborate and Seek Feedback

    Great work is rarely done in isolation. Graham emphasizes the importance of sharing your work early and often, and of surrounding yourself with the right peers. Good collaborators are a ‘force multiplier’—they can see things you miss, offer new perspectives, and push you to be better.

    Seek feedback not just from mentors, but also from peers who are working on similar problems. They understand the context and can give you practical advice. And don’t be defensive; use feedback to improve.

    In the startup world, this is why accelerators like Y Combinator are so effective. They provide a community of founders who share their progress and get feedback from each other, which accelerates their learning.

    Step 9: Maintain Resilience

    This is perhaps the most important quality: the willingness to work on hard problems for a long time. Expect setbacks, boredom, and self-doubt. They are part of the process.

    Graham warns that you will often feel like you’re not making progress, or that your work isn’t good enough. This is normal. The key is to keep going, to maintain the discipline to show up and work even when you don’t feel like it.

    Think of it like training for a marathon. You don’t run 26.2 miles on your first day. You build up gradually, and you have days when you want to quit. But if you stick with it, you eventually cross the finish line.

    Step 10: Prioritize Work-Life Balance as a Means, Not an End

    Finally, Graham argues that rest and play are not the opposite of work; they are necessary for sustained creativity. Your brain needs time to relax and wander, which is often when the best ideas surface.

    But he’s careful to say that balance is a means to an end, not the end itself. The goal is to enable more and better work, not to avoid work. So, take breaks, pursue hobbies, and spend time with loved ones—but do it so you can return to your work with fresh energy and insight.

    For example, many writers find that taking a walk or doing a mundane task helps them solve a plot problem. The break allows their subconscious to work on the issue.

    Putting It All Together

    Graham’s advice is not a checklist but a mindset. It’s about approaching your work with curiosity, discipline, and a long-term perspective. You won’t do great work overnight, but by following these principles, you can create the conditions for it to emerge.

    The most important takeaway is to start. Choose a problem that excites you, learn everything you can, and begin working on a project. Iterate, seek feedback, and stay resilient. Over time, you’ll produce work that is uniquely yours and that contributes something new to the world.

    Paul Graham’s ‘How to Do Great Work’ is not a magic formula but a practical philosophy. It reminds us that greatness is not reserved for a lucky few; it’s available to anyone willing to work deliberately and persistently. By choosing meaningful problems, developing your taste, and embracing the iterative process, you can produce work that matters. The journey may be long, but the rewards—both personal and professional—are worth it.

    Summary

    • Great work is a process, not a gift: it requires deliberate effort and iteration.
    • Choose problems that deeply interest you and seem important; follow your ‘ambitious curiosity.’
    • Master the existing knowledge in your field to reach the ‘frontier,’ where you can spot ‘cracks’ and ‘seams.’
    • Work on projects, not just skills, and iterate based on feedback and your own taste.
    • Cultivate resilience and embrace ‘slow hunches’—great ideas often develop over years.

    FAQ

    Q: What is the main idea of Paul Graham’s essay ‘How to Do Great Work’?
    A: The main idea is that great work is not the result of raw talent alone but of a deliberate, iterative process. Graham outlines steps like choosing interesting problems, learning to the frontier, finding ‘cracks,’ working on projects, and maintaining resilience.

    Q: How do I choose what to work on?
    A: Choose something that interests you deeply and seems important. Follow your ‘ambitious curiosity’—the combination of genuine fascination and a desire to make a difference. Don’t pick a topic just because it’s trendy; pick one that you find yourself thinking about even when you don’t have to.

    Q: What does ‘getting to the frontier’ mean?
    A: It means mastering the existing knowledge in your field so you understand the current state of the art. Once you’re at the frontier, you can identify the ‘interesting anomalies’—the gaps, contradictions, or unexplored areas where great work often emerges.

    Q: Why is working on projects important?
    A: Projects force you to produce tangible output, which is where real learning and iteration happen. Skills are necessary, but they’re only useful when applied to a specific goal. Projects give you something to show, evaluate, and refine.

    Q: How can I stay motivated when working on a long-term project?
    A: Graham emphasizes resilience and the willingness to work on hard problems for a long time. Expect setbacks and self-doubt, but keep going. Also, take breaks and maintain a work-life balance as a means to sustain your creativity, not as an end in itself.