FME 1000 Midterm Study Guide

Core idea

Entrepreneurial Thought and Action, or ET&A, helps entrepreneurs choose how to act when the future is uncertain. It combines prediction logic with creation or effectual logic, often called CreAction in the course.

CreAction sequence

1. Start with who you are, what you know, and whom you know.
2. Take a small action that you can afford to lose.
3. Observe the good, bad, and unexpected results.
4. Bring in people or resources that can help.
5. Adjust the next action based on what you learned.

Knittr application

Kayden uses prediction logic when he discusses investors, a complete website, inventory, and a warehouse before proving a customer problem. Under uncertainty, a better step would be to manually make a project recommendation and compatible shopping list for several actual knitters. That experiment uses resources at hand, limits loss, and produces information.

Common mistake

CreAction does not mean acting randomly or refusing to plan. It means matching the size of the commitment to the quality of the evidence.

Core idea

A Rocket Pitch communicates the customer problem, target market, proposed solution, and value proposition clearly and quickly. The goal is to make the logic easy to follow, not to list every feature.

A useful pitch order

1. Name the specific customer.
2. Show the problem with a concrete fact, behavior, or short story.
3. Present the proposed solution.
4. Explain the benefit and why it is meaningfully different.
5. Give a reason to believe the team can deliver the promise.
6. End with the next action, test, or request.

Three value-proposition tests

• Overt benefit: Why should the customer care?
• Dramatic difference: Why choose this over current alternatives?
• Real reason to believe: Why should the audience trust the promise?

Team presentation practice

• Divide responsibility by idea, not by arbitrary sentence counts.
• Make handoffs clear so the pitch sounds like one argument.
• Rehearse for time and remove details that do not support the main claim.
• Use feedback to revise the logic, not only the delivery.

Knittr application

Kayden should not lead with AI or a long feature list. He should identify a researched customer, show the difficulty that person experiences when choosing a project and compatible supplies, and explain one focused benefit. AI belongs in the pitch only if customer evidence shows that it improves the benefit.

Idea versus opportunity

An idea is an early insight about a problem, an unsatisfying solution, or a possible use of technology. An opportunity connects a defined customer and meaningful unmet need with a solution that can be delivered and sustained.

A promising opportunity is:

• Attractive: customers care enough to act.
• Durable: the need and advantage can last.
• Timely: conditions make this a sensible moment.
• Value-creating: the offer produces a benefit the customer values.

Knittr is currently an idea. Spending in the crafting category does not prove that a specific segment has the pain Kayden assumes or will switch to his offer.

Problem identification

Start with what the customer is trying to accomplish, where the current process breaks down, and what workaround already exists. Do not begin with the founder's preferred product.

As a [specific person in a context], I need a way to [make progress or solve a pain] without [important obstacle or tradeoff].

A possible Knittr statement, which still requires research, is: “As a newer knitter with limited free time, I need a reliable way to choose a project that matches my ability and buy compatible supplies without comparing scattered patterns, yarn requirements, and stores.”

Brainstorming rules

• Go for quantity.
• Stay focused on the topic.
• Be visual.
• Build on and combine other ideas.
• Have one conversation at a time.
• Defer judgment.
• Encourage wild ideas.

Strong brainstorming process

1. Write a customer-centered “How might we?” question.
2. Use a short creative warm-up.
3. Give everyone silent individual ideation time.
4. Share and cluster ideas without judging them.
5. Combine ideas and seek variety.
6. Only after generating many options, evaluate customer value, desirability, feasibility, viability, and possible tests.

Using AI for idea generation

AI can generate variations, combine interests, explore perspectives, and push beyond the first obvious answer. It cannot establish that an idea is true, desirable, or practical. Humans should supply context, verify facts, and use customers and experiments to judge the ideas.

Human-centered design

Design thinking is an iterative, team-based process for creating value from the customer's perspective.

1. Empathize: Observe and interview people in the context of their lives.
2. Define: Turn the evidence into a customer-centered problem statement.
3. Ideate: Generate many possible responses.
4. Prototype: Make a promising idea testable at low cost.
5. Test and iterate: Watch users, learn, and revise.

The central shift is from “What product do I want to build?” to “What problem is the customer already experiencing?”

Observation and empathy

Observation shows what people actually do, including workarounds and details they may forget to mention. Empathy means understanding another person's circumstances, feelings, behaviors, and needs well enough to see the problem from that person's perspective. It is different from sympathy and from immediately trying to fix the situation.

For Knittr, Kayden could observe how people choose a project, compare yarn, seek help, abandon work, and react when supplies are unavailable.

Discovery interviews

• Interview people outside close friends and family.
• Begin broad, then ask for details.
• Use open “how,” “why,” and “tell me about the last time” questions.
• Ask for real stories and past behavior rather than future predictions.
• Listen more than you speak.
• Probe neutrally and remain willing to be wrong.
• Record specific behavior, frustration, workarounds, and short quotations.

Weak: “Would you use an AI crafting app?”

Strong: “Tell me about the last time you chose a new crafting project. What did you do from the first idea to buying the supplies?”

Knittr application

Kayden lacks empathy evidence because he does not knit and has not studied the experience of actual crafters. His family interview leads participants toward his solution. He should investigate the problem before pitching Knittr.

Customer and consumer

The customer is willing and able to pay. The consumer or user experiences the product. They may be the same person, but a venture must identify who decides, who pays, and who uses.

Segmentation and target market

Market segmentation divides a broad market into groups with shared needs, traits, interests, or behaviors. Segments may use demographics, geography, psychographics, behavior, or need. The target market is the specific group the venture chooses to serve first.

“Women who craft” is too broad. A more useful starting segment might be beginner and intermediate knitters who complete several projects per year, find patterns online, and struggle to match those patterns with suitable yarn. Research must still test whether that group is attractive.

Customer personas

A persona is a fictional representation of an ideal customer grounded in patterns from interviews, observation, polls, demographics, and behavior. It should explain relevant pains, goals, constraints, workarounds, buying criteria, and channels.

Kayden's “Beatrice” is weak because her cats and K-dramas come from assumptions. A memorable detail belongs in a persona only when it helps predict a real decision.

Value proposition

A value proposition explains why a specific customer chooses one offer over alternatives. It should:

• Resonate: address an important need or pain.
• Differentiate: offer a meaningful advantage.
• Substantiate: give a reason to believe the promise.

For [target audience], who need [pain solved or desire fulfilled], [product] is a [category] that [compelling benefit], because [reason to believe].

Features describe what the product has. Benefits explain what the customer gains. Add “which means that…” after a feature until the statement reaches a result the customer values.

Business model introduction

A business model explains how the venture creates value, delivers it, and captures part of it as revenue. The nine Business Model Canvas blocks are customer segments, value proposition, channels, customer relationships, revenue streams, key resources, key activities, key partners, and cost structure.

Core idea

A prototype is an early representation of an idea built to answer a question. Its value comes from what the team learns, not from how finished it looks.

A useful early prototype is:

• Focused on an important assumption.
• Fast and inexpensive enough to change.
• Concrete enough for a customer to react or behave.
• Tested with members of the target segment.
• Revised based on evidence.

Prototype sequence

1. Name the riskiest assumption.
2. Decide what observable result would support or weaken it.
3. Build the smallest test that can produce that result.
4. Watch what customers do and ask neutral follow-up questions.
5. Record the evidence and change the next version.

Minimum viable product

An MVP is the smallest usable version that can test whether the venture creates value for customers. “Minimum” does not mean careless. The version must still be credible enough to test the intended assumption.

Knittr prototypes

• A paper or clickable project-selection flow.
• A manually created project recommendation and supply list.
• A concierge test in which Kayden performs the future service himself.
• A landing page that tests which benefit earns sign-ups.
• A small preorder or price test before purchasing inventory.

Building the full platform would test too many assumptions at once and make change expensive.

Desirability, feasibility, and viability

An opportunity must reach the intersection of all three. A desired service that loses money is not viable. A profitable-sounding product that the team cannot deliver is not feasible. A deliverable product that customers do not value is not desirable.

Demand, competition, and alternatives

Estimate demand with evidence from a defined segment, not the size of a broad category. Compare direct competitors with indirect alternatives and the customer's current workaround. For Knittr, alternatives include yarn stores, pattern sites, blogs, social media, Ravelry, Etsy, advice from friends, and doing nothing.

Resources, capabilities, and risk

Assess what the team knows, whom it knows, and what it controls. Name capability gaps rather than hiding them. Test the assumptions whose failure would most threaten the venture before making expensive commitments.

Financial, social, and environmental effects

Opportunity evaluation should include customer-acquisition costs, order economics, inventory risk, returns, supplier practices, packaging, labor, accessibility, privacy, and honest impact claims. A good business creates economic value while considering its effects on people and the planet.

Knittr application

Kayden should test desirability with real crafters, feasibility through manual delivery and knowledgeable partners, and viability through price and cost experiments. Positive comments alone do not satisfy all three lenses.

Research types

Begin with qualitative research when the team does not understand the problem well enough to form useful hypotheses. Use quantitative research later to test frequency, compare segments, or estimate demand.

Sampling

A useful sample includes people who represent the decision the team is studying. Convenience samples are easy to reach but often biased. A small qualitative sample can reveal themes; it cannot prove the size of a market.

Unbiased questions

• Ask one clear question at a time.
• Avoid wording that signals the preferred response.
• Ask about real behavior before opinions about a new idea.
• Use open questions for exploration and carefully designed closed questions for measurement.
• Include options that allow disagreement or uncertainty.

Focus groups

A focus group is a moderated discussion among potential customers that uses participant interaction to develop insight.

• Recruit about five to eight people from the target segment.
• Use a neutral moderator and an additional note-taker when possible.
• Prepare six to eight short, open questions.
• Move from easy and general questions toward the concept.
• Encourage participants to respond to one another.
• Prevent domination and invite quieter members without leading them.
• End with a question that asks what the team missed.

Kayden's family discussion is weak because he uses a convenience sample, pitches first, discourages criticism, and treats praise as confirmation.

Analyzing feedback

Look for repeated behavior, explanations, strong emotions, workarounds, contradictions, and disconfirming evidence. Separate what participants said from the team's interpretation. Turn themes into hypotheses for a later test.

The 4Ps and revenue drivers

• Product: the offer, benefit, and differentiation.
• Price: what the customer pays and why.
• Place: where and through which channel the offer is sold.
• Promotion: how the target customer becomes aware of it.

Revenue depends on the number and quality of customers, purchase frequency, the selling process or channel, and price.

Core idea

Organizational culture is the shared system of values, beliefs, assumptions, and norms that tells people how work is really done. Culture appears through repeated behavior, stories, rituals, language, rewards, status, and the actions leaders tolerate.

Formal rules versus informal norms

A rule is explicit and usually written. A norm is an informal expectation that develops through repeated interaction and reinforcement. When the two conflict, people often follow the behavior that the group actually rewards.

If a charter says meetings start at 6:00 but the team always waits for influential late members, the real norm is 6:15.

Visible and invisible culture

Visible culture includes schedules, dress, language, rituals, workspace, and stated policies. Invisible culture includes assumptions about status, conflict, effort, trust, risk, and who is allowed to influence decisions.

Positive and negative team norms

Useful norms make it easier to coordinate, speak honestly, meet standards, and learn. Harmful norms can normalize lateness, silence, domination, hidden work, or avoiding accountability.

Team charters

A useful charter turns aspirations into behavior. It should clarify purpose, roles, decision methods, meeting expectations, communication, conflict, accountability, and how the team will revise its own process.

Four abilities

• Self-awareness: recognize your emotions, patterns, strengths, and limits.
• Self-management: regulate impulses and choose a useful response.
• Social awareness: notice other people's emotions, perspectives, and needs.
• Relationship management: use that understanding to communicate, influence, resolve conflict, and maintain working relationships.

Responding rather than reacting means creating a pause between an emotional trigger and an action. The emotion may be valid, but the first impulse may damage the team or misread the facts.

Leadership application

A leader who sees an incomplete draft, assumes laziness, and posts an angry accusation shows weak self-awareness and self-management. If the role and deadline were unclear, the case also contains a process problem. The leader should check the facts, repair the public harm, and clarify the owner, deliverable, standard, and deadline.

Trust model

Trust = Authenticity + Logic + Empathy

• Authenticity: I believe you are genuine and consistent.
• Logic: I believe your reasoning and competence.
• Empathy: I believe you understand and care about my experience or interests.

A sincere and caring leader who recommends major spending without evidence may have authenticity and empathy but still lose trust through weak logic.

Three outcomes of team effectiveness

1. Performance: The output meets the needs of customers or stakeholders.
2. Learning and adaptability: Members and the team become more capable.
3. Member well-being and growth: The work remains sustainable and worthwhile.

A team can earn a high grade and still be ineffective if two people do all the work, nobody learns, and members refuse to work together again.

Conditions that support effective teams

• The right mix and number of people.
• Trust, mutual respect, psychological safety, and constructive conflict.
• Clear roles, decisions, deadlines, facilitation, and next steps.
• Alignment with the larger system, including authority, resources, and stakeholder feedback.

Psychological safety

Psychological safety is a shared belief that the team is safe for interpersonal risk-taking. Members can ask questions, admit uncertainty, raise concerns, disagree, suggest unusual ideas, and discuss errors without expecting humiliation or exclusion.

It does not mean constant agreement, low standards, or freedom from accountability. A team can debate strongly while protecting each person's ability to speak.

Actions that build safety

• Leaders acknowledge their own fallibility.
• Ask directly for dissent and concerns.
• Respond to bad news with curiosity before evaluation.
• Give members roughly equal opportunities to contribute.
• Thank people for revealing errors.
• Separate criticism of an idea or behavior from an attack on the person.
• Follow up so speaking up produces visible value.

Failure versus mistake

A failure is an unwanted result from testing something genuinely uncertain. When the test is thoughtful, the result can create useful information. A mistake ignores known information, violates an established process, or repeats a known error.

Constructive conflict

Task conflict debates evidence, assumptions, and choices. Relationship or status conflict attacks people. Useful responses restate the shared goal, ask for evidence, distribute airtime, name emotional escalation, and agree on a decision process.

Process gains and losses

Teams gain from combined knowledge, motivation, error checking, role modeling, and a shared map of expertise. They lose value through social loafing, poor coordination, dominant speakers, fear, hidden information, overload, and premature consensus.

Team leadership levers

1. Design: Clarify the purpose, membership, roles, timing, authority, and resources.
2. Launch: Build shared understanding of goals, capabilities, strategy, leadership, and norms.
3. Process management: Monitor progress and intervene when the team needs to adjust.

A team may need a relaunch when membership, purpose, or working assumptions change substantially.

Core idea

DiSC is a shared language for behavioral and communication preferences. It is not a measure of intelligence, worth, competence, or fixed ability. Everyone can use all four styles, and people should not be reduced to a label.

Flexing styles

The goal is to adapt communication to help the team work. A D can pause and invite input. An I can document commitments. An S can raise disagreement earlier. A C can identify the minimum evidence needed for a timely decision.

When a D wants speed and a C wants more data, the team can set a decision deadline and agree on the minimum evidence needed for a reversible test. This respects both preferences without declaring one style correct.

Diversity of thought

Different expertise, networks, backgrounds, opinions, personalities, and experiences can increase creativity and reduce groupthink. Those differences create value only when the team has norms that allow information to surface and influence the work.

Avoiding stereotypes

Use a profile as a prompt for conversation, not as permission to predict everything about a teammate. The individual remains the best judge of whether the description fits.

Personal and social identity

Personal identity includes characteristics and experiences that shape how a person understands themselves. Social identity connects a person with groups and categories that may influence belonging, status, opportunity, and how others respond to them.

Some differences are visible; others are invisible or context-dependent. A team should not assume that it knows which identities matter to another person or how that person experiences them.

Identity mapping

An identity map helps people reflect on the identities they notice often, those others notice, and those that shape access or expectations. Its purpose is awareness and discussion, not forcing disclosure or turning a person into a category.

Diversity, inclusion, and belonging

• Diversity: Who is present and what differences exist?
• Inclusion: Whose voice, information, and perspective can influence the work?
• Belonging: Do members feel accepted as legitimate parts of the group?

A team may be diverse without being inclusive. Asking a new member for ideas and then repeatedly ignoring them gives the appearance of participation without real influence.

Bias and assumptions

Bias can affect whose ideas receive credit, who gets interrupted, which behavior is considered professional, and who receives high-visibility work. Teams should examine patterns in decisions and outcomes rather than relying only on good intentions.

Faultlines and subgroups

Faultlines divide a team into stable subgroups, such as veteran and new members. Information may remain inside each group, weakening shared ownership and collective intelligence. Cross-subgroup tasks, shared goals, transparent decisions, and a wider team identity can reduce the division.

Inclusive leadership and decisions

• Distribute airtime and prevent repeated interruption.
• Ask for views before senior members anchor the discussion.
• Use clear decision criteria.
• Explain how input affected the final choice.
• Rotate meaningful responsibilities and visibility.
• Make it safe to question assumptions.
• Avoid requiring people to disclose identities or represent an entire group.