How I Built Ignited Workspace
A workspace for transformation delivery, knowledge sharing and programme visibility that teams could actually keep current.
Ignited Workspace was built as a central place for transformation teams to organise delivery information, working documents, updates and knowledge. The problem it solved was familiar: important context scattered across chats, decks, folders and individual memory.
How I Built It
I designed the workspace around the questions teams ask every week: what is the latest status, where is the source document, who owns this item, what decision was made, and what needs attention next. The structure followed the work, not an abstract filing taxonomy.
The workspace combined Microsoft 365 tools, SharePoint pages, document libraries, structured lists, automation and dashboards. The intent was to make it easy for teams to keep information current as part of their normal delivery rhythm.
What It Does
Ignited Workspace gives teams a shared home for programme materials, status visibility, decision logs, working templates, announcements and knowledge assets. It reduces searching and helps new joiners understand the programme faster.
What I Learned
A workspace succeeds when it becomes part of how the team works, not another place to update. The structure has to reduce friction immediately, or people will return to private folders and chat threads.