Back to skills
B1skills20 mins

Finishing What You Start: Simple Rules for Project Success

Analyze and discuss: Finishing What You Start: Simple Rules for Project Success

Article Summary

Many people start small projects but often do not finish them. The article explains why. It says we sometimes enjoy starting new things more than the hard work of finishing them. The writer shares four common problems: choosing too many new tools, making things too complex, adding too many features, and being afraid to launch. To help finish projects, he suggests a rule: launch a simple, working version within 48 hours.


Key Vocabulary

Project

Click to reveal

Abandon

Click to reveal

Motivation

Click to reveal

Skill

Click to reveal

Tool

Click to reveal

Launch

Click to reveal

Feature

Click to reveal

Prototype

Click to reveal

Scope

Click to reveal

Develop

Click to reveal



Comprehension Questions

1. What is the main reason the author says projects often fail?

  • a) Because people lack the necessary skills.
  • b) Because there is not enough time to finish them.
  • c) Because starting projects is more enjoyable than finishing them.
  • d) Because too many users try to use the project at once.

2. What is the 'Perfect Stack' Trap about?

  • a) Using only old and boring technology.
  • b) Choosing too many new and complex tools when starting a project.
  • c) Building products for millions of users from the very beginning.
  • d) Not having enough tools to start a project.

3. What does 'optimizing for phantom users' mean?

  • a) Making a product ready for real customers who are waiting.
  • b) Making a product for people who will probably never use it.
  • c) Making a product too complex for users who don't exist yet.
  • d) Not making the product fast enough for its expected users.

4. What is 'Feature Creep'?

  • a) Releasing a product with only a few basic features.
  • b) Adding too many extra features to a project, making it difficult to finish.
  • c) Being afraid to launch a project because it is not perfect.
  • d) Making a product simple and easy to use.

5. What is the '48-Hour Rule' for?

  • a) Working on a project for exactly 48 hours without a break.
  • b) Spending 48 hours planning a project before starting to build it.
  • c) Launching a basic, working version of a project within two days.
  • d) Waiting 48 hours after an idea before starting a new project.

Discussion Prompts

1. Have you ever started a project at work that you did not finish? What happened and what did you learn?

2. Which of the problems described in the article (e.g., too many tools, too many features, fear of launching) do you think is most common in your professional life?

3. How can the '48-Hour Rule' (or 'Two-Day Rule') help you or your team in future work projects or tasks?


Teacher Notes

This lesson focuses on common challenges in project management and strategies for completion, useful for executive learners. Encourage students to share personal experiences related to the discussion prompts. The grammar section reinforces practical language for giving advice and expressing necessity in a business context. Ensure vocabulary is understood before moving to comprehension questions.


Ticket to Class

Have you ever started a project at work that you did not finish? What happened and what did you learn?

Loading...