Class 11: September 22, 2026 · ENTR 5500
Notes from September 22, 2026. These notes record the discussion and instructions given that day. For current requirements and due dates, use the assignment guidelines and semester schedule.
Class slides · ENTR Announcements slides
Today’s focus
We used the Frank Addante and Apple cases to think about decisions, trust, and what makes a founding team work. The slides contain the case frameworks; these notes emphasize what our discussion added and what to do next for the entrepreneur interview project.
Learning from founders without turning them into heroes
The Addante recap returned to changing motivations, equity as a tool, the three Rs—roles, relationships, and rewards—and hiring and developing people as the venture changes.
Our discussion complicated those takeaways. Adaptation can mean improving an approach; a pivot is a larger change in direction. Experience does not eliminate mistakes. Learning requires noticing what went wrong and accepting responsibility, including the costs borne by employees and collaborators. Those costs include time and opportunities, not just money.
A case gives us a limited view of a person. We can criticize a decision without pretending we know everything about its maker. We can also learn from someone’s accomplishments without endorsing everything they did.
Satisficing means selecting an option that meets an adequate standard; optimizing means searching for the best available option. The useful question is how much attention a decision deserves. Spending too long perfecting a minor choice can crowd out a consequential one. This connects entrepreneurship to judgment: knowing which decisions matter and when enough information is enough.
Apple: complementary skills do not settle questions of trust
Jobs and Wozniak brought different strengths to the venture: technical creation alongside vision, persuasion, and assembling resources. A founder does not have to fill every role, and being a founder, an owner, and an employee are different relationships.
The Wozniak discussion asked what to do when a partner’s conduct damages trust. Confronting the partner, changing the working relationship, and leaving were all defensible possibilities to examine. The issue was larger than recovering an old sum of money: what does the incident tell you about future decisions together? Personal history can help a team, but friendship alone does not resolve expectations about power, work, or rewards.
When we graded the founding team, commercial success and team quality did not always receive the same grade. Complementary abilities can produce remarkable work while conflict and mistreatment impose real costs. A successful outcome does not demonstrate that harmful behavior caused—or was necessary for—that success.
The slides’ talent triangle offers another way to examine a team:
- Domain knowledge: understanding the subject, industry, or problem.
- Operational experience: knowing how to deliver the work and run the business.
- Business acumen: recognizing opportunities and bringing together the people, resources, and decisions needed to pursue them.
These capabilities depend on context. They are a useful way to identify what a team has and what it still needs.
AI can change which small ventures are worth doing
The book-reselling example showed AI helping with the work around a sale: identifying books from photos, researching sold listings, preparing descriptions and images, and organizing shipping. Pirate Ship was the shipping resource mentioned.
The entrepreneurial point was the cost of all that administrative work. Reducing it can make a small transaction more practical. Human judgment still matters: represent condition honestly, think about what a buyer needs to see, and check the proposed work before acting.
Thursday, September 24: group-project workday
Thursday is a workday rather than a formal class meeting. Use it to move from identifying an entrepreneur to preparing a useful conversation. Consult the Final Group Project tab in the course syllabus.
By the end of Thursday:
- Send your entrepreneur specific possible dates and times for an interview. You need to make the scheduling request; they do not need to have replied by that deadline.
- Post evidence of that outreach, such as a screenshot, in your team’s Slack channel.
- Share an accessible link to a substantial rough draft of your interview plan in that channel. Include questions, timing, and who will ask what.
Plan an initial conversation of approximately 30–60 minutes, with a 15–30 minute follow-up later. Aim to have the initial interview by mid-October. Tailor questions to what you already know and what you still need to learn.
Organize the plan around these six areas:
- Origin: what the founder noticed and how they moved into action.
- Business model: how the venture creates value for customers and captures value for itself; use the Business Model Canvas to guide your thinking.
- Resources and tradeoffs: how the founder obtained money, people, space, equipment, or other resources, and what those choices cost.
- Reducing risk: what they tested or learned and which decisions changed as a result.
- Founding-team dynamics: roles, relationships, rewards, power, and incentives.
- Challenges: unresolved problems as well as difficulties that have a satisfying ending.
The quiz shown on the copied slides was deferred in class. The stated focus for Thursday is this project work; no additional assignment was announced as due for that workday.
Resources and opportunities
- Steve Jobs’s 2005 Stanford commencement address: the discussion about connecting the dots in hindsight.
- Folklore.org: firsthand stories from the original Macintosh team.
- BlackBerry: the film mentioned as another founding-team story.
- Harry Frankfurt’s On Bullshit: the reading mentioned in the discussion of persuasion and indifference to truth.
- Startup Social: Thursday, September 24, 4–7 p.m., West End Zone of Sanford Stadium; Pitch Karaoke at 5 p.m. No venture or pitch is required to attend.
- Create Club: Monday, September 28, 4:30 p.m., Studio 225. A university photographer was announced for this meeting. RSVP.