2020-11-11 Hypha Worker Co-op: Business Planning
from template | Meetings | Calendar | Tasks | Code | Drive
Time: 3:00-4:00pm ET
Location: https://link.hypha.coop/calls
Attending: pc, dc, uv
Cultivator: dc
Notetaker: pc
Summary
- we’re committing to our capacity-planning spreadsheet for now
- https://link.hypha.coop/capacity-planning
- it should tell us (1) what’s in pipeline, and (2) what are gaps/needs
- re: pipeline. needs tidy, and some legend to capture diff between
- probability of work and
- intensity of work if acquired
- re: skills gap. will create lightweight skills matrix (h/t dc) with LEAD/SUPPORT/GROW/NO
- business plan is awesome and mostly needs immediate tidy, and then next version in 2021
- lacking focus on showcase, so future bizdev coworks will strive for blog post output
Agenda
Item | Time (min) |
---|---|
Personal Checkins | 5 |
Announcements | 5 |
Task Board Review | 15 |
Discussions | 30 |
Process Checkout | 5 |
Notes
Pre-game
- https://resources.platform.coop/
- uv: shared doma.city (art => company)
- infra vs platforming as way to align movement
Personal Checkins
- …(skipped)
Discussions
-
tcn/tomesh project framing/documenting
- #todo dc follow up with elon 1:1
-
#allhands capacity tracking (gantt charts?)
-
uv: what we this needs to do:
- what is coming down the pipe?
- dc: rn, just on/off, no sense of hours. something missing
- pc: dollars in spreadsheet? maybe proxies for work.
- MATRIX:
- this month/maybe/not
- low/med/hi work
- what skills are needed? what are skills gaps?
- goal: to know what we can do in-house
- dc: how do we even categorize our skills? what does that look like in a spreadsheet?
- e.g. DSF project
- start by looking at gaps?
- skill matrix
- #todo get member self-identification of skills
- want a sense of LEAD versus DO, WANT TO LEARN/SHADOWING
- pc: d&d character as skills? too complicated
- spreadsheet for now. raw dump
- dc: 15 min followup with ppl?
- raw dump. refining into set.
- #todo get member self-identification of skills
- colors: what do they mean in sheet?
- probability vs intensity of work
- probability is kinda below (?)
- circle/color = intensity over time
- #idea using unicode shiz
- #todo dc: update to sheet
- skills
- legend
- updating symbol in monthly columns
- splitting up categories
- types (“validation” sheet)
- client
- grant – we wrote a grant for a project we have developed
- didn’t write all of them. don’t need to worry about how ppl hiring us got money.
- internal – project inside hypha, not revenue generating or initated by outside org
- member – hypha is one of multiple stakeholders #todo UPDATE. stakeholder
- solidarity – we’re doing this at a reduced raite
- dc: important to know propertion of work from one-off grants vs ongoing client work vs product etc
- perhaps mostly tracking grant vs non-grant
- uv: from bizdev view, mostly concerned about how sales cyles differs. getting an idea of where we should be spending our time to develop new revenue streams.
- dc: revenue streams?: service, project, client, grant
- #todo create shortlink?
- what is coming down the pipe?
-
Y2 strategy and Business Planning
- https://docs.google.com/document/d/1U8C1XZcDpu1r4ciecbKEZ6vOL41nTinfqPCbZDhkAWc/edit#heading=h.f6mly1vag6ug
- aka https://link.hypha.coop/business-plan
- dc: looking back and these are fuckin legit goals
- worked on goal 1 (secure more projects) the last few months
- dc: suggested #todo, quick cleanup, then call it done
- ruthless 30min tidy session
- 2021 rewrite
- uv: biggest gap = showcase work more
- dc: #idea treat cowork as meeting session for blog post. +1 uv pc
- uv: #todo long list of terrible blog post ideas
- dc: miro for storing ideas? +1 dc, -1 uv
- close Y2 issue at end of next bizdev plan call
Process Checkout
- …
Action Items for Cultivator
-
Migrate items with
#todo:person
to task board -
Publish meeting notes as
- business-planning: open access, or publicly indexed with restricted access
- finance: open access, or publicly indexed with restricted access
- governance: open access, or publicly indexed with restricted access
- infrastructure: open access, or publicly indexed with restricted access
- operations: open access, or publicly indexed with restricted access
- Reset meeting pad for next meeting