Case: How to organize work on an Internet project in Trello


    Hi my name is Dima. I want to share with you the experience of working on the Carrot Quest service  (link to the project description on Megamind). This is a service for communicating and managing users based on their behavior, in other words marketing automation.

    For a long time we were looking for a convenient form of work and how many tried various tools: we used the Asana service, worked with Scrum boards, even managed to write tasks in Google Docs. We were constantly looking for a methodology convenient for the whole team.

    It seems we found what we were looking for. We want to tell you about this methodology and service.

    About us

    We combined the most important tools of Internet marketing in one service: eCRM, online chat, pop-ups, email newsletters and web analytics. Synergy is a key element, it is simply huge. Knowing about the actions of your user, you are more likely to engage him and bring to the purchase.

    Several programmers, a designer, a content marketer, an analyst and others are working on the project tirelessly. The whole team does one thing in one office, although sometimes there is remote work.

    Here are our main tasks:
    • product development;
    • layout;
    • mobile app development;
    • service design;
    • site design;
    • content marketing (articles, cases, news, reviews, etc.)
    • analytics (how our actions affect key indicators).

    This is how we organized the work on the project.

    After checking a bunch of services, we settled on the most optimal one -  Trello .


    The reasons are obvious:
    • Trello is very easy to use for the whole team;
    • It is ideal for task management;
    • no less important: it is free.

    The tool is so excellent that it’s not a pity to give money for it, but for some reason they chose such a business model.

    In the service you can create a large number of different boards (boards) that consist of sheets:


    Boards are interconnected, and cards with tasks can be transferred not only from one sheet to another (within one board), but also from one board to another . Just a couple of mono keys add a picture to the task, responsible, leave a comment, etc. In general, it's cool.

    Scrum boards in Trello

    Every startup and SaaS service should be developed according to Agile, so we first used the Scrum methodology.
    • We run weekly sprints;
    • On Saturday, an analysis of the sprint and planning the next;
    • Releases are launched when ready.

    We made several boards on the project:


    HADI Board

    HADI (Hypothesis, Action, Data Collection, Conclusions) is a methodology that we recently talked about in detail . With its help, IIDF has pumped over 150 startups. In fact, the methodology is quite simple.

    1. The hypothesis.

    At the beginning of the week, we put measurable hypotheses. Each hypothesis must be tied to a specific metric in order to understand what it is aimed at and to evaluate it later.

    For example, if you put a video about the service in the first block of the main page, the conversion to registration will increase by 5%.

    2. Action.

    Do everything you need to test a hypothesis.

    For example, prepare and record video, add subtitles, install video on the site, etc.

    3. Data collection.

    Start collecting data on indicators that are affected by the hypothesis. In our example, this is an indicator of transitions to registration. In addition, you can watch video viewing rates and% registered after watching a video.

    4. Conclusions.

    At the end of the week, draw conclusions. If the hypothesis is confirmed, then it is worth working on it and improving it; if not, then test the following hypothesis.

    Since in HADI every change is tied to some metric, we had a constant problem. A bunch of tasks, a bunch of ideas, a mess .... It is difficult to ensure that these indicators are always tied to the task.

    Trello helps us a lot with this.


    We created a board, which is divided into several sheets:
    • Planned (or ideas) - a sheet in which lies a bunch of ideas and tasks that are not yet solved. There was an idea - recorded here.
    • It does not affect the metric, but it is important - not every task affects a metric. Or defining a dependent metric is very difficult. For example: “build and modify all jscss”. In general, without a clue what this will affect, but it must be done.
    • CPA - tasks that affect the rate of CPA.
    • Sreg is all that will help improve the conversion to registration, as yet hypothesis.
    • Activation is an indicator that determines whether a user understands the value of a product. We have a separate technique for calculating it.
    • C1 - conversion to purchase, that's all that affects it.
    • C2-Cn - similarly, only repeat purchases.

    In fact, these are different stages of a regular sales funnel. We see how many upcoming tasks we have, and most importantly, what stage of the funnel they affect. If today the main problem for the project with activation and C1 is, then we begin to solve the problems from sheet C1 and Activation.

    It is very important that the comments on each task indicate the current numbers for these indicators (we are still trying to indicate where it is better). For each metric we made our own color - this was done for a reason.

    Six seconds, I’ll tell you.

    At the beginning of each HADI cycle, we take several unverified hypotheses and throw them onto another board (a board with current tasks). So that during further work you understand what metrics are influenced by the tasks being solved. Previously, it didn’t look so structurally and visually with us, now any of the team understands everything in a split second.

    Product board

    Presented and conducted daily work on the project.

    This is where the daily work on the project is reflected. Here's how it works:
    • “Tasks for the week” - here are the tasks that we planned for the current week or moved them from the HADI board.
    • “In the process” - when each employee begins to solve a problem, he simply drags it here;
    • “Done in a week” - the task is over, so I got here;
    • “Bugs” are all bugs that need to be resolved.
    • “Made in March” (or another month) - At the end of any month, we can see what exactly was done for the period and how it affected. This information helps shape our news.

    As you noticed, a color is assigned to each task, this color relates them to the HADI board metrics. The whole team sees what the task will affect. When collecting data, we add new indicators in the comments to the tasks. We draw conclusions and decide whether to return back or continue the changes.

    So we organized our work. This helps to make the whole process understandable, and most importantly, controlled. The key here is to see how changes affect our project.

    With pleasure, the Carrot Quest team .




    If you liked the article, the following materials will be useful:

    1. What tools do we use to work and communicate with users

    2. How we integrated our service with Slack

    Also popular now: