Creating and managing a plan

2 min read

When the user chooses to create a new plan, the display changes to show the ‘Plan’ tab.

This tab panel has itself three subordinate tab panels.

  • Planning: This has a set of inputs and controls that show the plan scope and expectations
  • Review: This tab shows the progress against plan during the plan period, and will be used at the end of the plan to record observations and outcomes.
  • Tasks: This tab shows the tasks associated with the plan and their current status in a Kanban view.

Planning panel #

With the ‘Planning’ panel the user can:

  • Record their view of plan prospects for the plan period
  • Record a journal entry to capture their thoughts and observations around the plan
  • View a burn down chart that shows the scheduled date distributions of plan tasks over the plan period
  • View the plan content by MIT, other tasks and habits
  • View the active goals and what progress is planned for each goal

When the user is happy with the content and structure of the plan, they can tap on the ‘Save’ to store and activate the plan.

Review panel #

After a plan has been saved the user may employ the ‘Review’ panel to:

  • Review progress during the plan period
  • Record observations and outcomes once the plan period has completed

When the plan period has completed, the user may record

  • Their opinion about the success of the plan
  • Create a journal entry to capture their thoughts and observations about the plan, its progress, outcomes and other issues.

At this point, the user should tap on the ‘Save’ disk icon button the close the plan.

Tasks panel #

At any point, whilst a plan is active, the user may select the ‘Tasks’ panel to view the status of tasks linked to the plan.

The tasks are displayed in a Kanban view, with separate tab column displays for tasks in ‘To-do’, ‘On hold’, ‘In progress’ and ‘Completed’ states.

Updated on March 23, 2025

What are your feelings

  • Happy
  • Normal
  • Sad
Newsletter
Subscribe Our Newsletter
This field is required.

Copyright @2025. Essays In Software. All rights reserved