Simple team output definition method

by mikilight1 in October 22nd, 2021

Like any other startup, we are also very keen to maximize the output. Otherwise, we are going to die.

What is mandatory for the startups is having a few vital, meaningful metrics to lead us to significant growth. We wanted a simple project management framework to focus on what matters to the growth.

Objective-Project-Task

And, we have started the objective-project-task classification. However, we were not comfortable enough to use the framework because what mattered to us was not clearly defining the work's significance. Our first assumption was that time is the key indicator to classify the results. Nothing is wrong with the objective-project-task classification. Everyone needs to chop the work into bite-size to make something happen. In reality, the type based on the time did not work out. We felt that our project board looked mishmash — not well organized. We also felt that there were too many project on the board.


Pillars of achievement type for the objective level

The first breakthrough was to organize the goal-setting on the extensive, objective level. We call it the pillars of achievement. There are a couple of goal types for startups, such as Product, Traction, Hiring, Fundraising, etc. We came up with the sub-goals to achieve the big goal. Now we got the nice pillars that we wanted to commit. However, uncomfortableness on the project level remained.


Degree of collaboration for the project level

A project is a set of works to get done to achieve the objectives. Before, we defined the project based on the time, assuming that a project that requires longer time is more significant. And, we kept feeling awkward somehow. There were critical projects and non-critical but time-consuming ones, are on the same board. And, we have noticed that the degree of collaboration among the team was the right question for us to define the project. For example, getting a certificate requires cross-functional collaboration. Once the work is adequately described upon the collaboration, every team member should own the bite-size task. Each member completes the bite-size task, and the team will be able to will complete the project.


The bite-size task for the task level

Now, we have the right objectives with suitable projects that will lead us to achieve the objective. The last piece is the task to accomplish the project. The last one is the task. The key is that the task has to be the size that each member can complete by themselves.

If you'd like to be a part of the UNiD EDGE community, visit our GitHub. Click Star🌟 if you like.

Your cart
    Checkout