This section is all about how Fuzzy Labs² works. It’s a new part of Fuzzy Labs, so you’ll see this page and subpages get updated as we embed processes and develop our operations. It contains the structures and processes that we use to set up and run projects as well as live operational information, such as departmental task lists and team allocation.

Principles

When setting up Fuzzy Labs² we wanted to set an ethos for how we’d work - the principles that we want to thread through everything we do.

This is what we came up with:

1. Do the right projects: we validate ideas against the three tests we’ve set to ensure that our projects meet the aims of the manifesto. This includes deciding if a project is novel and checking that it aligns with at least one of the United Nations Sustainable Development Goals
2. Measure progress: we define how we measure the success of individual projects and of Fuzzy Labs² as a whole
3. Take deliberate steps: we use project stages and research questions to structure our work
4. Open source, open minds, open experimentation: everything is done publicly, we value curiosity and share the journey as we go
5. Team effort: Fuzzy Labs² is a dynamic working group rather than a siloed department. We draw on experience and ideas from the whole Fuzzy Labs team, partners and the wider community

By defining structures and processes that directly link to our principles, the principles become second nature and just part of the normal way of working in line with the manifesto, just as they should do!

Structures and processes

These are the structures and processes for Fuzzy Labs², set up in order to deliver against the manifesto and in line with our principles.

<aside>

Definitions of project novelty

</aside>

<aside>

Measuring value and success

</aside>

<aside>

Project process

</aside>

<aside>

Research questions [WIP]

</aside>

<aside>

Communicating our work [WIP]

</aside>

<aside>

Team approach

</aside>

A note on tools and ways of working…

Fuzzy Labs² uses the same tools and general ways of working as everything else that happens in Fuzzy Labs.

Here in Notion we are holding our operational and project documentation; for team collaboration we use Slack. We use Jira for managing the day-to-day development work. All our code is open source in GitHub. Links to code repositories can be found within the specific projects

Operational information [WIP]

These are the pages with the live information used to manage Fuzzy Labs. It includes performance data in our KPIs and who’s doing what in the team.