Skip to project
← Projects

PROJECT_07 / Internal tooling & planning

Resource Allocation Tool

A phased proposal for replacing spreadsheet-based capacity planning.

STACKNext.js · Flask · PostgreSQL · Docker · RBAC

01

Overview

The original Excel tracker helped managers understand employee allocation and whether the team could take on additional projects. The proposal moved that workflow toward a shared web application.

My contribution

I defined a phased migration from Excel, planned the application and access model, and worked on the initial foundation and management dashboard in phase one.

02

The problem

As more stakeholders used the spreadsheet, version drift, collaboration limits, and weak change visibility made it harder to keep a reliable view of capacity. The goal was clearer planning and governance, not simply replacing Excel with a newer technology.

03

Phased engineering approach

The proposal separated an initial foundation from broader user workflows and project-specific planning.

  1. 01Next.js dashboard
  2. 02Flask services
  3. 03PostgreSQL records
  4. 04Docker services

Phase 1 · initial delivery

Login, database design, uploads, and a management dashboard for utilization and hours allocation.

Phase 2 · proposed

Employee pages, project creation, user management, role-based access, and profile editing.

Phase 3 · proposed

A project-specific planning dashboard complementing manager and employee views.

Technical decisions

Deliver in phases

Tie each phase to a concrete planning workflow rather than attempting the whole operational surface at once.

Plan governed access

User roles and ownership were requirements for a shared internal tool, rather than additions after the dashboard.

04

Planning challenges

01

Moving beyond one spreadsheet

Problem
A shared tool needs consistent records and clearer ownership.
Approach
Plan uploads, structured data, access control, and dashboard views together.
Result
Define a migration path that addresses workflow and governance.
02

Changing business priorities

Problem
A management change removed the need to continue development.
Approach
Keep the delivered phase distinct from proposed later phases.
Result
Stop after phase one without representing the roadmap as a completed product.
05

Result

The effort ended after phase one when management changed and the organization no longer needed the tool. The remaining employee, access-management, and project-planning phases stayed on the roadmap.

06

Lessons learned

  • Internal tools need a continuing business owner as well as a technical plan.
  • A phased scope makes partial delivery and changing priorities easier to evaluate.
  • Workflow, permissions, and data governance belong in the initial design.