Important Points 9 Phrases to Remember About Starting With the End in Mind

Key Points: 9 Sentences to Remember about “Starting with the End in Mind” #

Hello, I’m Zheng Ye.

The theme module of “Starting with the End in Mind” has been completely updated. I believe that through in-depth explanations of various practices, you have gained a more comprehensive and thorough understanding of this principle.

To help you review and revisit the content better, I have added a section called “Key Points” for each theme module. Now let’s go through the key points of the “Starting with the End in Mind” theme together.

  1. “以终为始”意味着在做任何事情之前，先要明确目标和期望结果。设定一个明确的终点可以为我们的行动指引提供方向和动力。

  2. 了解自己的核心价值观和人生愿景对于“以终为始”至关重要。它们可以帮助我们确定对我们来说真正重要的东西，并指导我们做出与之一致的决策和行动。

  3. 一个好的目标应该是具体、可测量、可行的和与个人价值观相符的。我们应该确保设定目标时充分考虑到这些因素。

  4. 想象和可视化自己已经实现了目标的情景可以帮助我们更加明确地设定目标，并激发我们追求目标的热情和动力。

  5. 在追求目标的过程中，我们要时刻牢记目标，并根据目标来设置优先级和做出决策。这样可以确保我们的行动与我们的目标保持一致。

  6. 制定长期和短期计划是实现目标的关键。长期计划可以帮助我们设定更远大的目标，而短期计划则可以指导我们在日常生活中采取行动。

  7. 建立良好的时间管理和自我管理习惯是实现目标的必要条件。我们要学会合理安排时间，充分利用每个时间段，避免无效和浪费的行为。

  8. 坚持和毅力对于实现目标至关重要。我们要克服困难和挫折，持之以恒地追求目标，并相信自己的能力和价值。

  9. “以终为始"是一种思维习惯，需要持续的反思和实践来发展和巩固。通过不断地思考和调整，我们可以更好地把握自己的人生方向，实现真正的成功和幸福。

希望这些关键要点能帮助你更好地理解和应用“以终为始”的原则，实现你的目标和梦想。如果你有任何问题或需要进一步的帮助，请随时联系我。谢谢！

Key Points: 9 Sentences to Remember about “Starting with the End in Mind” #

Hello, I’m Zheng Ye.

The theme module of “Starting with the End in Mind” has been completed completely updated. I believe that through in-depth explanations of various practices, you have gained a more comprehensive and thorough understanding of this principle.

To help you review and revisit, I have added a section called “Key Points” for each theme module. Now, let’s summarize the key points of the “Starting with the End in Mind” theme.

  1. “Starting with the End in Mind” means that before doing anything, you should clearly define the goals and desired results. Setting a clear endpoint can provide direction and motivation for our actions.

  2. Understanding our core values and life vision is crucial to “starting with the end in mind.” They can help us determine what truly matters to us and guide us in making decisions and taking actions consistent with them.

  3. A good goal should be specific, measurable, achievable, and aligned with our personal values. We should ensure that these factors are fully taken into account when setting goals.

  4. Imagining and visualizing ourselves having achieved the goal can help us set goals more clearly and ignite our passion and motivation to pursue them.

  5. In the process of pursuing goals, we should constantly keep the goals in mind and prioritize and make decisions based on them. This ensures that our actions remain aligned with our goals.

  6. Developing long-term and short-term plans is key to achieving goals. Long-term plans can help us set broader goals, while short-term plans guide our actions in daily life.

  7. Developing good time management and self-management habits are essential for achieving goals. We should learn to schedule our time effectively, make the most of each time period, and avoid ineffective and wasteful behavior.

  8. Persistence and perseverance are crucial for achieving goals. We should overcome difficulties and setbacks, persistently pursue goals, and believe in our abilities and worth.

  9. “Starting with the End in Mind” is a habit of thinking and requires continuous reflection and practice to develop and reinforce. Through continuous thinking and adjustment, we can better grasp our life direction and achieve true success and happiness.

I hope these key points help you better understand and apply the principle of “Starting with the End in Mind” to achieve your goals and dreams. If you have any questions or need further assistance, please feel free to contact me. Thank you!

Key Review #

In this module, we have learned some industry best practices.

  • DoD, the definition of done, to reduce internal misunderstandings within the team.
  • User stories, to refine valuable requirements.
  • Continuous integration, to reduce the amount of changes and the difficulty of integration by integrating early.
  • Lean startup, to reduce waste caused by overdeveloping uncertain products.
  • Iteration 0, to prepare some basics before starting a project.

We have also learned some important mindset shifts.

  • Everything needs to go through two creations: the first creation in the mind, which is the intellectual or mental first creation, and then the second creation, which is the actual construction or physical second creation.
  • Find your “end” within a larger context.
  • Find the path to your “end” by deduction.
  • Define your “end” with measurable “numbers”.

Practical Guide #

At the end of each article, we have condensed the entire content into a “one-liner” practical guide. We hope you can quickly get started and apply the principle of “starting with the end” in your actual work. Let’s review these practical guides together.

Additional Gains #

At the end of this section, I also provided answers to some popular questions that you may have during the learning process. I hope you understand:

  • As a developer, you can manage your superiors;
  • If a product manager mentions the boss, you can clarify things with the boss directly;
  • If a product manager likes mindless plagiarism, ask them to first figure out what they are actually copying;
  • Distinguish between requirements and technology, and let product managers and development teams each focus on their own tasks. - ——"Answering Questions | How to Manage Your Superior?"

Selected Comments #

The comments from classmates are lively and valuable. Wonderful comments themselves are a supplement and enrichment to the content of the article. Here, I have picked out some excellent comments to share with you.

When discussing the thinking framework for efficient work, classmate Zhang Wei-yuan mentioned:

The thinking framework is a road, and principles are evolved skills. From A to B, there are infinite paths, and the most effective one is the straight line. Essentially, each dimension and principle (not limited to the four principles mentioned by the author) helps us better locate where A is, where B is, and where the straight line is.

Regarding the principle of starting with the end in mind, classmate WTF mentioned:

“Starting with the end in mind,” the most common practice is reverse planning. Determine the time first, then see if the functionality cannot be accomplished and some features need to be cut off, if additional manpower is needed when the manpower is not enough, and anticipate and avoid risks in advance.

Regarding the acceptance criteria for user stories, classmate Liu mentioned:

The core responsibility of a programmer is how to implement product functionality and how to implement it; the premise is to understand the product functionality and what functionalities need to be implemented. Some project managers and product managers confuse their roles with programmers. When you talk about functionality with them, they talk about technical implementation with you, and when you talk about technology with them, they talk about product (what functionalities need to be implemented) with you.

Everyone is interested in sandtable deduction. Among them, classmate Xixi Fu and Kafka mentioned:

Through deduction, we can discover which departments and stakeholders are involved in achieving the goals, what resources are needed, and when and how they need to cooperate.

Classmate ZackZeng also commented on this topic:

Before a project goes online, there is usually a launch plan. For projects like database migration, not considering rollback during the launch is a design flaw in my opinion. Our company’s launch plan is usually written as a step-by-step checklist, and a peer review will be conducted before going online.

Classmate Scott also mentioned:

I don’t think it contradicts with doing a proof of concept (POC) and pre-deduction when the leader says to make it work first. Many times, we need a POC to prove that a project is feasible, which is actually part of the pre-deduction. Checking every detail before going online and quickly making the POC work are not contradictory. Of course, in the real world, everyone is eager to launch the POC as a formal product, which is the prelude to countless tragic stories.

Classmate Rest and Comeback made a good addition to the deduction process:

Before going online, there should be an expectation of which machines and what configurations are needed, and even prepare in advance.

Classmate adang also shared his enlightenment in his work:

To write clearly, you have to think clearly. This is a sentence that I highly agree with in programming work, and I also think it is an important difference between qualified and unqualified developers. In software development, the most common example is when you receive requirements and start coding without thinking, often results in continuous rework, and numerous quality issues. Moreover, the overtime work is endless. One fundamental reason behind this is the lack of systematic thinking. However, many people think that clarifying requirements, analyzing and designing are time-wasting, and only coding is the true value creation, which creates the gap.

When talking about using numbers to measure work as much as possible, classmate Xixi Fu and Kafka mentioned:

For example, developers often focus on whether the functions proposed by product managers have been implemented, but they should also understand how many people are using the developed product, and how many people are using each page. In addition, it is necessary to see whether developers are working hard, not just listening to what they say, but also looking at how frequent their git commits are, when they commit, and how much code they write. Code quality can be measured by the number of bugs/code. Of course, these quantifications may not be scientific and may even be misused, but they are better than making judgments solely based on impressions.

Classmate Da Bin also mentioned:

To postpone a plan for collecting data on a certain index last week. Without data, all plans are just empty words. AB testing, the number of comments, the number of readings, and the number of forwards, all data is the basis for the next step of decision-making and improvement.

Due to space limitations, I will share only this much. Thank you for the wonderful comments from classmates. Many classmates have raised various questions in the comments area, which can all be solved through task decomposition. Take it easy, the next topic we will cover is “task decomposition”.

Thank you for reading. If you find this article helpful, feel free to share it with your friends.