• English

      • Managing a Complete Project with Aino LifeOS

      This post uses "develop a new feature and ship it" as an example, showing how to use Aino LifeOS's PARA, tasks, calendar, and periodic notes to manage a two-week project.

      Kickoff: Create the Project Space

      Set Up in PARA

      Create the project in PARA's Projects category:

      1. Open the sidebar, navigate to 1-Projects/
      2. Create a new folder User-Notification-System/
      3. Create the project README README.md:
      ---
tags: [project, backend, frontend]
status: in-progress
deadline: 2024-04-15
---

# User Notification System

## Project Goal

Provide users with in-app and email notification capabilities.

## Milestones

- [ ] Database design & migration — Week 1
- [ ] Backend API development — Week 1
- [ ] Frontend UI components — Week 2
- [ ] Integration testing & launch — Week 2

## Related Docs

- [[Notification System Tech Spec]]
- [[Database Design Doc]]

      Break Down Tasks

      Create Task Breakdown.md in the project folder, refining milestones into actionable tasks:

      ## Week 1 Tasks

- [ ] Design notifications table 📅 2024-04-01
- [ ] Write database migration script 📅 2024-04-01
- [ ] Implement notification creation API 📅 2024-04-02
- [ ] Implement notification query API 📅 2024-04-03
- [ ] Implement mark-as-read API 📅 2024-04-03
- [ ] Write API unit tests 📅 2024-04-04

## Week 2 Tasks

- [ ] Notification bell component 📅 2024-04-08
- [ ] Notification dropdown panel 📅 2024-04-09
- [ ] Notification settings page 📅 2024-04-10
- [ ] Integration testing 📅 2024-04-11
- [ ] Bug fixes 📅 2024-04-12
- [ ] Deploy to production 📅 2024-04-15

      These dated tasks automatically appear in the task inbox and on the calendar on their respective dates.

      Week 1: Execution

      Daily Workflow

      Every morning, open your daily note:

      1. Check today's calendar time blocks — which tasks are scheduled
      2. Pick one from the task inbox and start a Pomodoro
      3. Write technical docs in the editor
      4. Discuss solutions with AI Chat when stuck

      Record Technical Decisions

      Create decision records in the project folder:

      # Tech Decision: Notification Storage

## Context

Choose notification storage: relational database vs message queue

## Comparison

| Approach           | Pros                               | Cons                              |
| ------------------ | ---------------------------------- | --------------------------------- |
| PostgreSQL         | Team familiar, transaction support | Limited under high concurrency    |
| Redis + PostgreSQL | High performance, real-time push   | Increased architecture complexity |

## Decision

Use PostgreSQL — current user scale doesn't warrant extra complexity.

## Follow-up

If DAU exceeds 100K, consider adding Redis as a notification cache layer.

      Reference with [[Tech Decision: Notification Storage]] in the project README.

      Track Progress in Daily Notes

      Record project progress daily:

      ## Notes

- Notification system: DB migration complete, API development 60% done
- Found an issue: bulk mark-as-read needs transaction performance consideration
- Discussed with backend colleague, decided to use batch UPDATE

      Weekend: Weekly Review

      Open the weekly note to review Week 1:

      ## Week Review

### Notification System Project

- ✅ Database design & migration — Complete
- ✅ Backend API development — Complete (all 6 APIs ready)
- Encountered bulk operation performance issue, resolved with batch UPDATE
- 2 items pending from code review

### Next Week Plan

- [ ] Frontend UI component development
- [ ] Integration testing
- [ ] Prepare for launch

### Risks

- Frontend components need interaction details confirmed with designer, potential blocker

      Week 2: Sprint & Launch

      Manage Deadlines with Calendar

      View all task deadlines in the calendar month view to ensure nothing is missed.

      If a day is overloaded, drag tasks to other dates to redistribute.

      Four-Quadrant Prioritization

      Switch to the calendar's four-quadrant view to prioritize by urgency/importance:

      • Urgent + Important: Fix test-blocking bugs
      • Important + Not Urgent: Improve error handling
      • Urgent + Not Important: Reply to design feedback
      • Not Urgent + Not Important: Code style improvements

      Project Complete: Archive

      After successful launch:

      1. Update the project README status to "Complete"
      2. Record the launch confirmation in your daily note
      3. Move the entire 1-Projects/User-Notification-System/ folder to 4-Archive/2024-Notification-System/
      4. The project disappears from the home view, but all docs and decisions are preserved

      Project Management Feature Map

      PhaseKey ActionsFeatures Used
      KickoffCreate project space, break down tasksPARA + Tasks
      PlanningSet deadlines, prioritizeCalendar + Tasks
      ExecutionFocus work, track progressPomodoro + Daily Notes
      CommunicationTech docs, solution discussionsEditor + AI Chat
      ReviewWeekly summary, risk assessmentWeekly Notes
      ArchiveArchive project, preserve docsPARA
      Tip

      The core of project management is "tasks visible, progress trackable." Give the project a space with PARA, give tasks time with the calendar, record daily progress in daily notes, and review periodically in weekly notes — this fits personal work rhythms better than any project management tool.