Files
zmVault/resolving-process-uncertainty.md
T

63 lines
1.2 KiB
Markdown

---
id:
aliases: []
tags:
- authorship/original
- destiny/permanent
- status/incomplete
- topic/organization
- type/guide
title: Resolving Process Uncertainty
---
# Resolving Process Uncertainty
## Process Uncertainty Resolution Steps
1. **Check your [[#Writing Process Notes|notes]]**
2. **[[#Asking Process Questions|Ask]] a ==peer== whose answers you trust**
3. **Ask your immediate supervisor**
Only escalate if you are still uncertain.
## Writing Process Notes
%% TODO: %%
### `TALK`
Taking notes has many benefits,
many of which I would not list as such
* **deferring responsibility:**
* **optics:**
note-takers always look more valuable than they would otherwise.
### Citation
When you get an answer to a [[#Asking Process Questions|question]],
or otherwise get some useful direction
that you expect to use later,
You should add it to your notes as soon as possible.
With any direction you should include:
* **who** said it,
* **when** they said it, and
* **what** it was in reference to.
```md
> [!quote]
```
## Asking Process Questions
Ask your question as succinctly as possible **first**,
provide background or complications **after**.
Prepare for any obvious clarifying questions.
### Choosing Your Target
%% TODO: %%