Hi @Guillaume_Soto, and thanks for attending our nonprofits webinar earlier today:
I wasn’t really familiar with logframe but have just skimmed a few articles including the one you linked. In order to represent this Asana’s free version, as you request, my quick answer would be the following (recognizing that it seems there are many versions of logframe and application to different-sized efforts would likely require different approaches than this, but it’s a start at lest!):
- Create Asana Project: “Effort X Logframe”
- In List View, create Sections, in order: Goal, Objectives, Outputs, Activities, Inputs
- In each Section, create Task(s) needed to address the topic of that Section (this will vary from effort to effort)
- For each one of those Tasks (except those Tasks under Inputs), use the same structure, either placing it in the Description field with rich text, or instead using Subsections (Tab+N while in Subtasks)/Subtasks instead, to capture the following information for each Task:
Objectively Verifiable Indicators
Means of Verification
There would be many benefits to using Asana for logframe.
Many of the built-in Asana benefits that would help to develop the logframe, e. g., the Comments thread on each to allow participants to discuss/improve, and all the other collaboration benefits inherent in Asana (notifications, etc.) would help out too.
Specifically the Activities Section’s Tasks are the bread and butter of Asana–work management. Those are a natural for using an app like Asana in particular, but all the other content is easily managed as well.
You surely have more experience than I do in logframe–what do you think? Is this a helpful start? Certainly with Premium or Business even more can be done, but I don’t think it’s required by any means.