Leave the work better than you found it.
A document someone else can understand. A process no longer dependent on memory. A system the next person can maintain. A lesson that does not need to be relearned. A relationship that still holds trust.
Good work does not only produce results. It creates the ability for others to continue.Read the manifesto
DELIVERY IS NOT THE END
Delivery completes a task. Stewardship prepares what comes after it.
The file was sentCan someone else understand it?
The feature worksWho will maintain it?
The campaign endedWere lessons preserved?
The client approvedAre next expectations clear?
The deadline passedWhere do remaining risks live?
Work is complete only when the next part can begin.
WORK SHOULD OUTLIVE THE WORKER
Work should not stop functioning when its creator leaves.
Not only one person has the password.
Not only one person understands the system.
Not only one person holds the relationship.
Not only one person remembers why decisions were made.
Not only one person can fix it.
Not only one person can continue.
A person's value does not decrease when they help others continue the work.
DOCUMENTATION IS CARE FOR THE FUTURE
Documentation is a message to people who were not in the room when a decision was made.
Decisions and reasons.
Processes.
System structure.
Access rights.
Known limits.
Risks.
Incident response.
Lessons.
Open questions.
Next directions.
Documentation is not secondary work. It is care for the future.
DO NOT BUILD DEPENDENCY AROUND YOURSELF
A strong contribution does not make everyone dependent on the contributor.
Hold informationShare context
Hold every decisionDelegate appropriately
Do everything aloneBuild team capability
Become a bottleneckCreate alternate paths
Prove indispensabilityMake the system less fragile
KNOWLEDGE SHOULD MOVE
Knowledge should move, not stop with the person who learned it.
Write down what was learned.
Teach someone else.
Create templates.
Build checklists.
Record common mistakes.
Share context.
Make reusable resources.
Let others improve them.
LEAVE SYSTEMS UNDERSTANDABLE
A system is not complete if no one else can understand it.
NamingNeeds consistency
StructureNeeds logic
ProcessNeeds hidden steps revealed
OwnershipNeeds clear responsibility
TestingNeeds a definition of working
ExceptionsNeed to be recorded
MAINTAINABILITY IS QUALITY
Maintainability is a form of quality.
Easy to update.
Easy to repair.
Not dependent on dying tools.
Does not create excessive handover cost.
Can expand.
Can be retired safely.
A fast solution that creates long-term burden may not be a good solution.
CARE FOR SHARED RESOURCES
Use shared resources knowing others will need them after you.
Team timeDo not waste it in purposeless meetings
BudgetDo not use it to hide poor decisions
DataDo not collect what is unnecessary
Brand reputationDo not trade it for short-term gain
User trustDo not overexploit it
InfrastructureDo not leave invisible cost
LEAVE RELATIONSHIPS IN GOOD CONDITION
Results should not be created by weakening relationships others still need to maintain.
Clients.
Partners.
Colleagues.
Communities.
Users.
Vendors.
CREDIT THE FOUNDATION YOU INHERITED
Stewardship begins by acknowledging that you inherited a foundation.
No one starts entirely from zero.
HANDOVER IS A HABIT
Handover is a habit throughout the work, not an event in the final week.
Documentation stays current.
Access is not owned by one person.
Decisions are recorded when made.
Knowledge is shared continuously.
Backup ownership exists.
A handover path is always ready.
KNOW WHAT SHOULD NOT CONTINUE
Stewardship is not preserving everything. It is deciding responsibly what should continue.
Unneeded dataDelete safely
Ineffective processStop it
Outdated documentationReplace or remove
Harmful productDo not continue because of sunk cost
Obsolete systemRetire with a plan
TECHNOLOGY NEEDS STEWARDSHIP
Responsible products prepare for change, failure and eventual closure.
Allow data export.
Record automated decisions.
Have recovery plans.
Clarify AI content sources.
Assign maintenance ownership.
Prepare for platform migration.
Plan for product shutdown.
STEWARDSHIP IN WORK IDENTITY
Work identity should not only say what you created. It should show what you helped continue.
DocumentationWhat you documented
ProcessWhat you standardized
SystemWhat you improved
PeopleWho you trained
KnowledgeWhat you transferred
RiskWhat you reduced
ResourcesWhat others can reuse
ContinuityHow others can take over
WHY FORWORK EXISTS
Forwork was built so long-term contributions do not disappear when a project or role ends.
So people can preserve context, documentation, processes, transferred knowledge and impact that continues after they leave.