Skip to content

Latest commit

 

History

History
61 lines (31 loc) · 1.85 KB

purpose-driven-action.md

File metadata and controls

61 lines (31 loc) · 1.85 KB
description
Let your activity serve an output. Let that output serve a business purpose.

Purpose Driven Action

All motion is not Progress

It's difficult to see the difference in the middle of an activity. The problem lies in our belief system.

Reference Start with Answer first | Effective Communication.

We are conditioned to start with what we know instead of what is needed to be done for the outcome to occur, irrespective of my current pool of knowledge.

Purpose-First

When starting to execute, take a pause. Start with a visual of what is that you want to occur. Then, backpropagate to visualizing the set of activities that will reckon its occurrence certain.

Let that view be persistent during all that you do henceforth, until output is achieved.

In this state, activity isn't the destination in itself, but a mere run-time requirement.

Not all Purposes are equal

At any given time, a team is optimizing for only 1 of the 4 variables, while keeping others:

  1. Speed Time
  2. Cost Time + Re-do.
  3. Quality Output
  4. Control Predictability **

Often the teams will be going through them in the same order.

Do less to do more

You can't push growth; you can only remove rate-limiting bottlenecks to growth.

This goes for individual growth too. You can't change a behavior. You can only change the underlying belief that causes it and then a behavioral change is its mere outcome.

Similarily for a team, seeing the better shared common view is the way to create any transformation.

Our beliefs are our only constraints.

Extending the Thought

{% embed url="https://twitter.com/ShaneAParrish/status/1298972029656264704" %}

A helpful read here would be:

{% page-ref page="alpha/asking-the-right-question.md" %}