List view
# 🧭 Milestone: Team Improvement / Operational Efficiency / AI This milestone focuses on **building a high-performing, resilient, and AI-augmented team culture**. Our goal is to continuously improve how we work — blending **technical excellence with human wellbeing**. ### ⚙️ Technical & Process Evolution We’re embedding **AI practices natively into our development flows** to enhance clarity, speed, and quality: - **Specification-Driven Development (SpecKit)** as our shared language of intent. - **Agentic workflows** and **MCP server usage** to automate repetitive tasks and surface insights. - **Improved cadence**, **feedback loops**, and **error handling** to strengthen delivery consistency and developer productivity. ### 🌱 Human & Cultural Dimension Operational excellence also means caring for the people behind it: - Fostering **psychological safety** — open communication, learning from mistakes, and trust. - Encouraging **ownership**, **participatory decision-making**, and **shared accountability**. - Sustaining **team energy, engagement, and balance**, ensuring improvements serve both people and performance. ### 💡 Vision By aligning **technology, process, and culture**, this milestone transforms AI from a tool into an **organic part of how the team thinks, collaborates, and evolves**.
Overdue by 2 month(s)•Due by December 31, 2025## Description Spaces, Challenges + Opportunities are all very similar to each other. Having 3 different concepts is simply very confusing for our users, as well as bringing a lot of complexity into the platform. The intention is to have a single entity, **Space**, that can then have child spaces i.e. subspaces. Then the different ways in which spaces are used, at different levels, is controlled by a combination of templates and UX design. Longer term it may also be that we want to support more than the 3 we essentially now support. Also a lot of customers / usage right now is satisfied with 2 levels. In essence this is about creating a general Space concept, which can then be adapted to support multiple types of usage / methodologies via the template that is applied. Currently the platform enforces a hierarchy with structure that is often not relevant / right: it needs to be more flexible. ## Initiative / goal Simplifying the platform, both for end users and in terms of functionality to be maintained. ### Hypothesis Space, Challenge and Opportunity can be represented by a single concept i.e. **Space** The term subspace is much easier for users to comprehend when using the platform as they have already internalized the concept of space. Space as a concept together with templates is rich enough to make a "challenge subspace", "goal subspace", "opportunity subspace"
Overdue by 1 year(s)•Due by June 1, 2024