Skip to content

Commit 236ca83

Browse files
committed
Edit: Look Outside Your Immediate Task, Maintain the Bigger Picture
1 parent d16000e commit 236ca83

File tree

1 file changed

+15
-15
lines changed

1 file changed

+15
-15
lines changed

README.md

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -228,21 +228,21 @@ Point of View for more context.
228228

229229
### Look Outside Your Immediate Task, Maintain the Bigger Picture
230230

231-
- When starting any task, take time to understand the rationale behind it (the
232-
WHY).
233-
- See how the task connects to broader goals, milestones, or parallel efforts.
234-
It may be part of a chain where upstream or downstream effects matter.
235-
- Maintain awareness of the bigger picture. A task that seems minor may be a
236-
critical blocker for a more visible effort. Conversely, something that appears
237-
simple might turn out to be time-consuming and affect teammates or
238-
dependencies.
239-
- With a deep understanding of the task, you will start seeing how different
240-
strategies (e.g., Strategy X vs. Strategy Y) can lead to different outcomes.
241-
This kind of insight allows you to:
242-
243-
- Escalate risks early.
244-
- Spot opportunities.
245-
- Align better with the system's or team's needs.
231+
When starting any task, take time to understand the rationale behind it (the
232+
WHY). See how the task connects to broader goals, milestones, or parallel
233+
efforts. It may be part of a chain where upstream or downstream effects matter.
234+
235+
Maintain awareness of the bigger picture. A task that seems minor may be a
236+
critical blocker for a more visible effort. Conversely, something that appears
237+
simple might turn out to be time-consuming and affect teammates or dependencies.
238+
239+
With a deep understanding of the task, you will start seeing how different
240+
strategies (e.g., Strategy X vs. Strategy Y) can lead to different outcomes.
241+
This kind of insight allows you to:
242+
243+
- Escalate risks early.
244+
- Spot opportunities.
245+
- Align better with the system's or team's needs.
246246

247247
A practical application of this mindset in documentation writing: start each
248248
technical page with a clear problem statement and a description of its

0 commit comments

Comments
 (0)