Partnership begins with responsibility
metatraining is open to partnership proposals. To me, a partner is not someone who helps the founder do his work, but someone ready to take part of the project as their own responsibility to the people for whom this project exists.
What I call partnership
Internal alignment with the project's approaches, boundaries, and purpose.
Independent responsibility for your own scope, not merely carrying out the founder's tasks.
Working first of all for the project's users, not for the founder.
Why I need a partner at all
My usual role in projects is to understand the problem, assemble a working system, test it, and hand over control. metatraining began the same way, but here there was no ready person from the start to whom the next scope could be handed.
Find a working solution
If no suitable method exists, understand the task, assemble a new scenario, and bring it to a working state.
Test the system
Check that the solution really closes the problem and that the system can work as more than the author's idea.
Hand over control
Transfer a stable scope to someone who can be responsible for it independently and develop it further.
- I do not seek to keep forever everything I have once built. To raise the next flag, the previous one needs to be in the hands of someone for whom it has become their own.
A partner is not the founder's employee
The form of cooperation can vary, but for me the meaning of partnership begins before money, title, or equity - with where a person takes responsibility for their part of the project.
Not this
Making the founder's life easier.
- waiting for tasks to be assigned constantly
- being responsible only to the founder
- supporting the project only while it is profitable work
- treating your area as someone else's property temporarily delegated to you
This
Taking part of the project on yourself.
- being independently responsible for your scope
- seeing users as the final recipients of your work
- developing the system rather than merely servicing it
- carrying the project's flag because the project itself has meaning
Partnership begins when part of the project stops being "the founder's task" for a person and becomes their own responsibility to those for whom metatraining exists.
A prerequisite
Before discussing a specific role, there is only one test - how internally aligned you are with the project's approaches and boundaries. Nobody can pass this test for you.
The project matters in itself
You see value not only in working with the founder, but in the fact that metatraining should exist and work for users.
The constraints make sense to you
You agree that the project does not choose goals for a person, does not treat them, and does not substitute for relevant specialists.
You do not need to be led by the hand
Given an independent area, you are ready to work things out, make decisions, and be responsible for the quality of the result.
Work for users
You see the quality of the project as an obligation to the people who have entrusted it with their goals and time.
What already exists
Partnership does not begin from a blank page. metatraining already has a concept, methodological architecture, product logic, research, public boundaries, and a working project language.
concept and methodology
The user's goal, achievement pipeline, practice, supervision, and transition between pipelines already form a connected system.
user journey
The project is developing as a practical tool for achieving goals, not as a knowledge library or the author's philosophy.
clear responsibility
metatraining is responsible for the quality of the tool and practice, but does not choose the user's goal and does not become an expert in its substance.
The exact partnership format is deliberately not fixed in advance. Role, scope of responsibility, economics, and form of participation only make sense after it becomes clear that the person and the project genuinely fit each other.
When it makes sense to write
I am interested in proposals where a person already sees not only their competence, but also the area of the project for which they could potentially take responsibility.
- The metatraining approach and boundaries feel internally close to you.
- You are ready to offer not only help, but your own responsibility.
- You are interested in an independent role, not constant management from above.
- You understand which part of the project you could make more stable or stronger.
Alignment does not mean identical views on every question. Partners can argue about methods and decisions. What matters more is that we do not need to renegotiate every time why the project exists and to whom we are responsible for its quality.
If this describes you
Read the project and author pages. If after that you see a possible scope for partnership, write directly and tell me what exactly you would like to take on.