T100

For T100, an event led by AKA, teams had to work together toward goals set by the head of AKA. The work was organised into broad initiatives, concrete plans and day-to-day tasks, and one piece of work could belong to several teams at once.

Plans like this usually live in a spreadsheet, one row per task. A spreadsheet can list the work, but it struggles with the simple questions: how far along is each initiative, which team owns what, and what is already late? And the progress had to be presented clearly at the event itself.

• Three levels: initiatives, plans and tasks
• Work shared between several teams
• Late work hard to spot
• Progress to present at the event

I built T100, a Hebrew web app that turns the plan into a living structure: initiatives contain plans, plans contain tasks, and every item can be assigned to one or more teams. Each task can record the measurable goal it serves, and completion is worked out automatically from task statuses, for every plan and every initiative.

A team-manager dashboard shows the whole picture or one team's view, with headline numbers, charts and colour-coded cards that count down the days to each deadline. A presentation mode turns the same data into slides for the event, one per initiative, and each initiative opens its own dashboard.

T100 gives the work toward the goals of the head of AKA one shared home: every initiative, plan and task in one place, linked to the teams responsible, with completion worked out automatically and a presentation ready for the event.

It also shows how quickly I turn a need into working software, and how I rework the foundations when the need changes: between the first and second versions I rebuilt the whole data model around teams.

I built T100 on my own, end to end. I designed the data model, wrote the server, built every screen by hand in JavaScript (cards, nested pop-ups, charts and the presentation slides) and prepared an installation package for computers without internet access.

I shipped three versions in seven weeks. After the first version I rebuilt the data model around teams, then added the presentation mode the event needed.

I worked with ChatGPT and Gemini as coding assistants. To make them useful on a real codebase, I wrote a small tool that packs the project's file tree and code into one briefing, so every new conversation started with the whole project in view. I designed the system, directed the work and decided what went into the code.