Skip to content

[epic] Micro Guide: Designing digital good business models (with public interest flavor) #70

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
10 of 25 tasks
rufuspollock opened this issue Apr 18, 2023 · 0 comments
Open
10 of 25 tasks

Comments

@rufuspollock
Copy link
Contributor

rufuspollock commented Apr 18, 2023

Designing digital good business models (with public interest flavor). Design Business Models for public interest digital goods like an emissions or environmental footprint database

Acceptance

  • Skeleton
  • Landing page for "fuller guide": designing business models guide
  • Draft

Tasks

Landing page

Notes

Parking lot re naming etc

TODO: this is an important issue. Get a "good enough to try" for now, plus a list of options documented for future re-consideration.

Parking lot

  • Digital public infrastructure
  • public interest digital infrastructure
  • public interest software, content and data
  • digital goods

Dimensions

  • Qualifier option
    • Public interest
    • public infrastructure
    • ...
  • Digital goods
    • digital good
    • digital product etc

Sketches

Excalidraw sketch (various iterations jan 2023 to march 2023)

Summary excalidraw with sketch of guide layout: https://link.excalidraw.com/l/9u8crB2ZmUo/AS49XMqTYbf

Guide outline 2023-03-30

🚩 sort of deprecated now as replaced by coggl plan above

What is our goal 2023-03-30? Here's a guide to designing the business model for a database of emission data (Aside: why emissions data? not important, we just want a concrete example)

  • Executive summary (last)
  • [Why, What] Production and supply of emissions data (digital goods in general) requires a different set of guiding principles and a richer/alternative set of approaches because digital goods are fundamentally different from "normal" goods [in being ~ costlessly copyable and having active disincentives for production/supply] 
  • [How] There are 6 basic archetypes for production and supply of emissions data (digital goods) and there are these criteria for assessing which are usable in which combination. [Designing socio-economic systems for digital information/data [Diginomics system design] builds on these 4 archetypes which can be combined in Z ways.] [epic] Incentive Model Taxonomy #22
    • 🔥 Introduction to business models and terminology Terminology and Glossary #39
    • How to assemble from building blocks (? even optional - don't have to explain in some mathematical way that X constraints lead to Y options - can be an appendix later)
    • 🔥 Resulting typology / taxonomy: i.e. list of models with a page for each model
      • visual overviews e.g. tree of models explaining
  • Evaluation system (in general) (how do you assess model) aka "Features" e.g. access, social value etc [optional]
    • Bonus is diagrams that rank by feature or that show how to choose a model by the features you want (e.g. you want open, then you have this)
  • How to choose for you "The discerning model buyer's guide to the best models" 😉 (nb: may move this to front at end!)
    • What key factors about your situation to consider
    • What features do you care about
    • Well, here is the shortlist ranked by X

Original outline of guide (coggle jan 2023)

Overall outline of plan of work: https://coggle.it/diagram/Y7wv5r1Eo51jzYBJ/t/diginomics-101

image

image

@rufuspollock rufuspollock changed the title [epic] Guide: Designing digital good business models [epic] Micro Guide: Designing digital good business models (with public interest flavor) Apr 18, 2023
@rufuspollock rufuspollock mentioned this issue Apr 18, 2023
70 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant