beancounter
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| beancounter [2018/11/14 21:14] – external edit 127.0.0.1 | beancounter [2018/11/28 15:04] (current) – Struct data changed splitbrain | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== BeanCounter ===== | + | ====== BeanCounter |
| Wikis cost money, right? Somebody' | Wikis cost money, right? Somebody' | ||
| Line 7: | Line 7: | ||
| And what better way to decide who pays how much than by measuring how much they use it? | And what better way to decide who pays how much than by measuring how much they use it? | ||
| - | ==== Usage ==== | + | ===== Usage ===== |
| This pattern makes perfect sense, if you ignore everything meaningful about what makes a wiki worth paying for in the first place. Since charging users proportionally to their use effectively punishes them for using it, it deters usage, braking and even reversing the virtuous cycle known generically as the network effect, in which value attracts users, who create value, in turn attracting more users. | This pattern makes perfect sense, if you ignore everything meaningful about what makes a wiki worth paying for in the first place. Since charging users proportionally to their use effectively punishes them for using it, it deters usage, braking and even reversing the virtuous cycle known generically as the network effect, in which value attracts users, who create value, in turn attracting more users. | ||
| Line 13: | Line 13: | ||
| Truly enough, if the value could be quantified, each expenditure of usage would be seen as a low-risk, high-gain investment, which would encourage use. But since it can't, there is no quicker way to kill a wiki than to announce that you will charge for usage. | Truly enough, if the value could be quantified, each expenditure of usage would be seen as a low-risk, high-gain investment, which would encourage use. But since it can't, there is no quicker way to kill a wiki than to announce that you will charge for usage. | ||
| - | ==== Example ==== | + | ===== Example |
| These are actually examples from other fields that show the network-effect-killing results of pay-as-you-go pricing: | These are actually examples from other fields that show the network-effect-killing results of pay-as-you-go pricing: | ||
| Line 22: | Line 22: | ||
| The problem in both of these cases was that every time a customer contemplated using the service, a calculation had to be made: will this make my monthly bill higher than I want it to be? Even though the answer was usually " | The problem in both of these cases was that every time a customer contemplated using the service, a calculation had to be made: will this make my monthly bill higher than I want it to be? Even though the answer was usually " | ||
| - | ==== Related Patterns ==== | + | ===== Related Patterns ===== |
| - | + | ||
| - | * [[Gate|Gate]] - in which barriers are placed before new users. The BeanCounter is worse, however, because instead of just providing one initial barrier, it punishes each user for each use. | + | |
| - | + | ||
| + | * [[Gate]] - in which barriers are placed before new users. The BeanCounter is worse, however, because instead of just providing one initial barrier, it punishes each user for each use. | ||
| ---- struct data ---- | ---- struct data ---- | ||
| + | classification.type | ||
| + | classification.focus : People | ||
| ---- | ---- | ||
beancounter.txt · Last modified: 2018/11/28 15:04 by splitbrain