Structure work
Turn an unclear request into an objective, a bounded scope and a definition of done.
Leaves behind
A brief people can act on.
Taipei, Taiwan
Ian Lee
I make complicated work easier to see, coordinate
and finish.
I structure unclear work, make ownership and blockers visible, and create documentation that helps people make decisions and continue the work.
Project · Program · Operations · ProductClear work. Traceable decisions.
01 — Work
What I do
Make the work visible.
Make the next step clear.
Coordinate work
Keep owners, dependencies, decisions and blockers visible as work moves.
Leaves behind
A shared view of what happens next.
Create evidence
Organize observations, results and decisions so someone else can inspect them.
Leaves behind
A record that supports a decision.
Improve processes
Use templates, checklists and clearer handoffs to reduce repeated reconstruction.
Leaves behind
A repeatable way to continue.
02 — Evidence
Selected work
The problem, the action,
and what exists afterward.
01Documentation · Working sampleA handoff someone else can continueA reusable note for the final state, evidence, unresolved items and next owner.Inspect the work
Illustrative template
This is a newly prepared working sample. It shows a structure for making a handoff explicit; it is not an employer document or a completed client engagement.
- Situation
- Work needs to move to another person.
- Problem
- A status label alone does not explain what is finished, what supports that conclusion or what remains open.
- Constraints
- The next person needs enough context to continue without reading every message.
- My role
- Specify a simple documentation structure, with this example prepared using AI assistance.
- What I did
- Separate the intended outcome, current state, evidence, open items and next action. Make ownership and acknowledgment explicit.
- Result
- A blank, reusable handoff record that can be completed for a real project.
- Limitations
- No claim of measured time savings, adoption or a client outcome. Those need to be tested in use.
- What happens next
- Use it on a bounded piece of work, ask the receiving owner what is missing, and revise the note.
02Scope · Personal projectFrom a broad brief to this websiteOne professional home, a clear content hierarchy and explicit boundaries on claims.Inspect the work
Personal project · 2026
This website is itself a small scope-and-delivery example. Ian supplied the direction; the implementation and initial copy were prepared with AI assistance.
- Situation
- Professional information and ideas existed across several platforms, without one place to explain the work.
- Problem
- A conventional résumé or a broad personal brand would not show how the work is structured and handed over.
- Constraints
- Keep maintenance low. Use public-safe content. Do not invent client results, testimonials or seniority.
- My role
- Set the positioning, content priorities and capability boundaries in the design brief.
- What I did
- Define a sequence: what I do, examples, method, writing, background and contact. Limit the first version to a readable, single-page site.
- Evidence
- The page you are reading, the explicit case structure and the downloadable working sample.
- Result
- An implemented professional website with inspectable examples and a consistent way to add future cases.
- Limitations
- This is not evidence of business traction, improved hiring outcomes or production software engineering expertise.
- What happens next
- Add verified case evidence and selected published writing as they become available.
Samples are labeled. No internal employer material is published here.
03 — Method
How I work
A clear outcome.
A bounded action.
A record someone can use.
The work ends with a clear final state, an owner and a next action.
- 01
Define the outcome
What has to be observably true for this to be finished?
- 02
Understand the current state
What do we know, and what still needs checking?
- 03
Make ownership visible
Who owns what, and where is a decision required?
- 04
Move one meaningful thing
Take a bounded action that produces information or progress.
- 05
Keep evidence
Separate what happened from what we think happened.
- 06
Surface blockers early
Make the uncertainty and the decision needed explicit.
- 07
Close or hand off
Leave a final state, a receiving owner and a clear next action.
04 — Notes
Writing
Questions from doing the work.
I’m collecting notes on coordination, delivery and testing business ideas. Selected published pieces will be linked here.
- Program operations
- Coordination across workstreams.
- Projects
- Scope, delivery, status and closure.
- Products
- Customer problems and small experiments.
- Entrepreneurship
- Selling, negotiation and running the work.
05 — AboutThe person
The person
behind the work.
Ian Lee
Based in Taipei, TaiwanI come from a technical work background, including Linux OS enablement and server validation. My focus is the structure around the work: coordination, documentation, evidence and a clear handoff.
I work best when the objective is explicit, progress is visible and the next action is small enough to carry out. I use trackers and checklists to make that possible.
Outside work, I spend time at language exchanges and I’m learning Thai. I’ve lived in Taiwan, South Africa and London; I use Mandarin and English.
Work history on LinkedIn06 — ContactHave work that
Connect on LinkedIn Have work that
needs structure?
Tell me what needs to be finished,
where it stands and what is getting in the way.