diff options
| author | Ben Sima <ben@bsima.me> | 2024-12-04 15:52:52 -0500 |
|---|---|---|
| committer | Ben Sima <ben@bsima.me> | 2024-12-21 10:08:05 -0500 |
| commit | 81cf94523f5a794e5b0c69dbd9a94619135a23c7 (patch) | |
| tree | 22544f9d741827ebfe65f73f0202b2b095a09cf8 /Biz/Pie.hs | |
| parent | 47c48abf836f5918120c0550c57d4eda32d3f10e (diff) | |
Prune unused stuff
This was all dead weight, just delete it and move on.
Diffstat (limited to 'Biz/Pie.hs')
| -rw-r--r-- | Biz/Pie.hs | 27 |
1 files changed, 0 insertions, 27 deletions
diff --git a/Biz/Pie.hs b/Biz/Pie.hs deleted file mode 100644 index 8de6ca6..0000000 --- a/Biz/Pie.hs +++ /dev/null @@ -1,27 +0,0 @@ --- | [P]roduct [I]mprovement [E]ngine --- --- A product improvement engine must measure two things: --- --- 1. Is your product built? --- 2. Do you have product-market fit? --- --- Let's use an analogy: building a startup is like jumping off a clif and --- assembling a plane on the way down. As we approach the ground at terminal --- velocity, only two questions are relevant: Is the plane built? Does it fly? --- Nothing else matters. --- --- So, Pie is a program that records answers to these two things and then --- reports on whether we are making the correct progress. --- --- This is inspired by a few things: --- --- - YC's Startup School has a build sprint questionnaire --- - Sam Altman's startup playbook: "You want to build a 'product improvement --- engine' in your company." --- - Sean Ellis' question: "How would you feel if you could no longer use this --- product? (a) Very disappointed, (b) somewhat disappointed, (c) not --- disappointed" and then measure the percentage who answer (a). -module Biz.Pie where - -main :: IO () -main = pure () |