Sharing the world of Fuzzy Labs² is essential! It’s how Fuzzy Labs² can generate commercial interest for Fuzzy Labs and to share the outcomes with everyone interested in advancing the state-of-the-art in MLOps.
It’s really just a simple table, but puts a structure in place for our communications. For anything we want to communicate, it helps us answer the questions like
In the table below, green rows are the priority while we get Fuzzy Labs² up and running. Red rows we’ll review over time.
| Communication name | Who is it for? | What are we communicating and why? | How is it communicated? | How often? | Who is responsible? | Where does the information come from? |
|---|---|---|---|---|---|---|
| MLOps WTF newsletter (section within existing) | Customers, partners | Top level project updates; outcomes; research themes | Monthly | Matt | Project pages | |
| Fuzzy Labs team update | Whole Fuzzy Labs team | Project progress, learning for application in BAU | Team meetings; Slack; demos | Varying | Matt - summary; Team members - detail | Project pages; team members |
| Fuzzy Labs board meeting update | Fuzzy Labs Directors | Performance metrics; strategy | Board meetings | Monthly | Matt, Tom | KPI register |
| Social media features | Customers; potential customers; MLOps community | highlights; examples of positive impact; team member profiles; lab notes | LinkedIn; MLOps community Slack channels | ad-hoc - at least fortnighly | Tom | Project pages; team members |
| Research papers | MLOps community | Technical detail of discoveries | Published on Fuzzy Labs website; publicised through LinkedIn, MLOps community Slack channels | ad-hoc | Matt, with input from team members | Project pages; GitHub; team members |
| Project Notion pages | MLOps community; Customers; potential customers; | Research questions; research; planning; experiment descriptions; outcomes; learning | Open access to Fuzzy Labs² Notion pages | always available; signposted during other comms | Team members BAU activity | Team members BAU activity, reference to GitHub where needed |
| Lab notes | Whole Fuzzy Labs team; Nerds; Partners; Academic partners; MLOps community; Customers; potential customers; | Progress; Results; day-to-day plan; challenges for nerd sniping | Fortnightly | Team members, Matt | Project pages; GitHub; team members | |
| Lab drop in | Partners; Academic partners; MLOps community; Customers; potential customers; | demos, ideation, progress, deep dive, interaction. Will be different content each time - e.g. a demo one time, then deep dive the next, or interactive coding, Q&A | Webinar | Monthly | Matt | Project pages; GitHub; team members |