Teki is a one meeting methodology for projects building. Teki means drop (of water) in Japanese. The main idea is doing small progress day by day in the process of building your project.
This methodology is ideal for:
- Small teams without full time to dedicate.
- Track the progress so that prevent to lose the north
- Share the past decisions to new members or stakeholders
- Projects that depends on people feedback (video games, social movements, events, etc)
- Projects that wants or need fast learning and progress
Teki Tracking Document: Pitch Deck:
Teki consist in one single meeting. This meeting needs to be done every week, but you can have it in any moment inside the week if you need.
graph TD;
week(Teki completed)-->teki_meeting[Teki Meeting];
question(You or your team has questions)-->teki_meeting[Teki Meeting];
lost_the_north(The Project lost the north)-->teki_meeting[Teki Meeting];
other(Whatever good reason)-->teki_meeting[Teki Meeting];
before_start(Before start to work in some new feature)-->teki_meeting[Teki Meeting];
teki_meeting[Teki Meeting]-->Teki
teki_meeting[Teki Meeting]-->pd[Pitch Deck]
teki_meeting[Teki Meeting]-->progress_doc[Teki Tracking Document]
One important thing before start every Teki is being aware of what is the stage of your project:
Goals
- Discovering initial necesities, ideas, concepts
- Create your first Pitch Deck
Your are here if You do not have nothing
You are not here when
- You have the initial idea of what you want to build.
- You already have a Pitch Deck
How much time you should be here Not to much preferable, couple of weeks or couple of months, depends in what you want to build. Keep in mind this stage is just an initial step to put together in a document what you are doing.
AKA: Minimum valuable product
Goals
Your are here if
You are not here when
How much time you should be here
AKA: Product Market fit
/ Discovering if there is a match between the market and your product (startup)
- ... (I don't have any experience with this part)
In every stage you have to undersand that your goal is different so don't waste your time to get hundreds of clients if you not even know what’s your product, what's your market and what you want.
Every member of the team has to be prepared for the meeting
- You are not an expert (If you were you don't need Teki and probably you have your project completed or your startup is already successful), so don't assume nothing
- Prepare the data for the meeting. What data? any kind of data: interviews, analytics, meetings, comments, etc, better if comes from your customer/client. Don't you have clientes? See next point.
- Client: you, your friends, your colleagues, your family, people in forums, etc.
- Use a monthly or single document (Confluence, Wiki, source code, word, google docs) to track the progress.
What the team learned since the last meeting, The most important learning should be took from the client, but every kind of learning is welcome. Write all the learnings
Present the data you have collected in the last Teki. Write down the most important part.
Write all the ideas that comes from Learnings and Data first, finally your ideas.
why yes, goals whay are you trying to answer
why not