United States
| No | Text |
| 1 | Andreasklinger #product #metrics #marketingstartup lessons learned |
| 2 | How ı think about code management |
| 3 | Quick tips for hiring remotely |
| 4 | Close your office. now. how to operate your startup under lock-down. |
| 5 | #fyi: how founders can avoid drive-by-management |
| 6 | Refactoring larger legacy codebases |
| 7 | A model that’s mental |
| 8 | Managing remote teams - a crash course |
| 9 | The simplest and most important dashboard for early stage startups. |
| 10 | Easy, but easy to f*ck up. 3 rules to setup analytics tools correctly. |
| 11 | A primer on startup metrics – which analytics tool to pick. |
| 12 | You should follow me on twitter. ı got a literature prize for my tweets. no kidding. proof with aboutpage ;) |
| No | Text |
| 1 | Code management 101 |
| 2 | Reduce complexity |
| 3 | ıncrease confidence |
| 4 | A continuous process |
| 5 | Tl;dr |
| 6 | Let’s go&h****ip; |
| 7 | Let’s get started&h****ip; |
| 8 | Feel free to stop reading here |
| 9 | Different setups of remote teams |
| 10 | Process needs |
| 11 | Hybrid setups are hard to do |
| 12 | Default remote or default non-remote? |
| 13 | Why would a team want to work remotely? |
| 14 | ıteration vs. innovation |
| 15 | Loneliness |
| 16 | Optimize for iteration - optimize for single player |
| 17 | But&h****ip; these are not problems of remote teams |
| 18 | Aren’t you already working in some way? |
| 19 | The end |
| 20 | The segmentation of web analytics |
| 21 | First: please lower your expectations |
| 22 | Exploration vs accounting |
| 23 | External vs ınternal analytics |
| 24 | ın a nutsh**** |
| 25 | Which tools |
| 26 | Specialised tools |
| 27 | The big problem with all tools |
| 28 | Work with your database for accounting |
| 29 | #about |
| No | Text |
| 1 | How do you reduce complexity? |
| 2 | Concepts with better boundaries |
| 3 | Remove code |
| 4 | A quick note on extractions |
| 5 | How to increase confidence? |
| 6 | How to ensure new code is better? |
| 7 | Single player mode |
| 8 | Technical migrations |
| 9 | Taking inventory |
| 10 | Create time |
| 11 | How to handle inbound: |
| 12 | Cultural differences |
| 13 | How to evaluate |
| 14 | Synchronize |
| 15 | Contract-to-hire |
| 16 | Hope this helps |
| 17 | First up: we are the lucky ones |
| 18 | As a team leader you have the following todo list |
| 19 | Understand the situation |
| 20 | Own the moment and communication |
| 21 | Working from home - help your team to optimize their daily routine. |
| 22 | Remote work - set your processes up to function remotely |
| 23 | Forced self-isolation and the feeling of loneliness |
| 24 | Being worried about family |
| 25 | Schools will get closed |
| 26 | Have succession plans |
| 27 | Nice-to-haves |
| 28 | Ok, we are done&h****ip; what next? |
| 29 | Thanks for reading |
| 30 | You got this. |
| 31 | There is a useful method for this |
| 32 | 1) get the team on board |
| 33 | 2) plan for “health by a thousand small improvements.” |
| 34 | 3) don’t a***ume different = bad |
| 35 | 4) create space |
| 36 | 5) create non-blame culture |
| 37 | 6) automate whatever you can automate |
| 38 | 7) ıntroduce tests |
| 39 | 8) acknowledge tech debt |
| 40 | Example: meetings |
| 41 | Digging deeper: managing remote engineering teams |
| 42 | Early stage startup metrics |
| 43 | The one “dashboard” i recommend almost all early stage startups is one they already have. let’s start using it. |
| 44 | Seriously? that has nothing to do with metrics, or? |
| 45 | Put one person in charge of keeping all customers on green. most likely that person is you. |
| 46 | Customer happiness ındex |
| 47 | Commercial break. |
| 48 | Rule #1: as few actions as possible |
| 49 | Rule #2: triggered by the same logic in code |
| 50 | Rule #3: same names in every tool |
| 51 | That’s it |
| 52 | Let’s roll&h****ip; |
| 53 | Exploration are those ad-hoc questions. |
| 54 | Accounting are the metrics we track over time. |
| 55 | About data integrity |
| 56 | Google analytics: |
| 57 | Kıssmetrics and mixpanel |
| 58 | So to answer the question – which tool would i recommend |
| No | Text |
| 1 | Rule #3.1 event names: be understandable |
| 2 | Rule #3.2 event names: be explicit |
| No | Text |
| 1 | how you manage your code |
| 2 | two tasks |
| 3 | Reducing complexity |
| 4 | Increasing confidence |
| 5 | continuous process. |
| 6 | solve complex problems |
| 7 | breaking them apart |
| 8 | easier |
| 9 | solve complicated problems |
| 10 | eureka |
| 11 | highly |
| 12 | Fewer parts |
| 13 | Fewer interconnections |
| 14 | fewer parts |
| 15 | fewer interactions |
| 16 | Example: |
| 17 | you should be able to write down the concepts in your app in simple English sentences |
| 18 | you should be able to point at the specific representations/abstractions |
| 19 | removing code |
| 20 | when tasked |
| 21 | you know how to solve it |
| 22 | Minimize the ways things |
| 23 | obvious |
| 24 | those ways work |
| 25 | Automate |
| 26 | explicit processes |
| 27 | new code you add is better than the old one |
| 28 | automate |
| 29 | process |
| 30 | The magic trick: |
| 31 | quantify your code quality expectations |
| 32 | which technical migrations |
| 33 | Create time |
| 34 | you started a migration |
| 35 | Sometimes global coherence is better than local perfection |
| 36 | original state |
| 37 | ideal end state |
| 38 | decision/plan |
| 39 | explicit |
| 40 | 80% of a migration |
| 41 | rarely for the last 20% |
| 42 | death through thousand cuts |
| 43 | Introduce Fix-It Friday |
| 44 | know the migrations |
| 45 | know what’s important |
| 46 | creates peer pressure |
| 47 | authority |
| 48 | hope this helps |
| 49 | What issues do you face when you hire remotely? |
| 50 | Your Take-Home Challenge |
| 51 | Your pair-programming session |
| 52 | How much should the freelance rate be? |
| 53 | Close your office. Now. (2) |
| 54 | But |
| 55 | Right now: |
| 56 | In the next weeks: |
| 57 | The current situation we face is not about “remote work”. |
| 58 | forced isolation |
| 59 | forced work-from-home |
| 60 | global pandemic |
| 61 | not to become a fully functional remote team overnight |
| 62 | first goal |
| 63 | establish an emergency work-from-home setup |
| 64 | My Recommendation: (2) |
| 65 | My Recommendation |
| 66 | To minimize any initial shock: (2) |
| 67 | Once you feel comfortable: |
| 68 | Resources |
| 69 | How you can help: |
| 70 | How to help them |
| 71 | If you are reading this blogpost for the first time feel free to skip this part. |
| 72 | Create confidence and focus by going the extra mile |
| 73 | Organization |
| 74 | Management: |
| 75 | This is your moment to step up as a leader. |
| 76 | Suggestions by founders |
| 77 | might often be misunderstood as directions or decisions |
| 78 | we didn’t intend this |
| 79 | A team discusses something |
| 80 | founder |
| 81 | replies that they like option B |
| 82 | most likely contender |
| 83 | option A |
| 84 | thought through in detail, prepared and pitched |
| 85 | might have caused more harm than help |
| 86 | Drive-by management at its worst. |
| 87 | this was completely non-intentional |
| 88 | The key in avoiding this, is being explicit. |
| 89 | add a short line |
| 90 | might mean very different things in different cultures |
| 91 | specific code |
| 92 | explained in their team-internal wiki |
| 93 | #fyi: |
| 94 | #suggestion: |
| 95 | #recommendation: |
| 96 | #plea: |
| 97 | all the time |
| 98 | much less |
| 99 | entirely unused |
| 100 | #fyi: i found this article about how founders can avoid drive-by management. |
| 101 | “code that doesn’t get touched dies” |
| 102 | anxiety (2) |
| 103 | raw excitement |
| 104 | imposter syndrome |
| 105 | you are challenging yourself |
| 106 | slight panic |
| 107 | you care a lot about quality |
| 108 | to come up with something smart to say |
| 109 | best possible people |
| 110 | anger |
| 111 | is just hope and pa***ion |
| 112 | wanting to scream and run through any wall |
| 113 | sometimes overwhelmed |
| 114 | push yourself |
| 115 | not too weak |
| 116 | too crazy |
| 117 | normal |
| 118 | you are normal |
| 119 | see your fear |
| 120 | your attention being awake |
| 121 | see your worries |
| 122 | your love for detail |
| 123 | look back |
| 124 | what you already achieved. |
| 125 | look forward again |
| 126 | Written for us both to remember. |
| 127 | still had anxiety in situations |
| 128 | exciting |
| 129 | anxiety is just misled excitement |
| 130 | rethinking of my situation |
| 131 | thankful for my body trying to help me |
| 132 | excitement |
| 133 | your raw excitement |
| 134 | COVID-19 Update: |
| 135 | Remote teams need 5x the process. |
| 136 | At Product Hunt we thought a lot about this! Here a few answers that helped us: |
| 137 | Remote work is the logical evolution of digital work. |
| 138 | A personal relations***p to this customer will tell you his story. |
| 139 | put someone in the team in charge of making sure everyone stays on green. |
| 140 | product insights - simple ways to use my database information to create actionable insights. |
| 141 | If you have only 0 - 100 new signups don’t hide them neither |
| 142 | And as soon as someone moves to orange contact them via email or skype. |
| 143 | Churn is not happening when a user unsubscribes from your service or stops paying you. |
| 144 | Don’t treat them as numbers, if you don’t want to be treated the same way. |
| 145 | But to be honest, as fancy this is, i hardly ever need this. |
| 146 | less moving parts |
| 147 | Protip |
| 148 | My recommendation: |
| 149 | the event should be triggered at the place the data change happened. |
| 150 | Most of the questions i get are based on a few misunderstandings. |
| 151 | Disclaimer: |
| 152 | If you are hoping to add one tool and be ready to go |
| 153 | readjust your expectations |
| 154 | All tools are good for a few things, but tend to suck for most of the other |
| 155 | Any tool |
| 156 | not optimal for all of your usecases |
| 157 | not specific enough |
| 158 | most likely be broken or incorrect |
| 159 | contradicting every other tool |
| 160 | But that’s ok. |
| 161 | exploration / accounting. |
| 162 | external / internal |
| 163 | very often related to some intuition we have. |
| 164 | Conversion Rates, Landing Page Optimizations, Funnel Optimizations, Viral Loops, Quick questions and insights are they typical examples of usecases of exploration. |
| 165 | KPIs in your excel sheets |
| 166 | includes reports here we tend to use several times a week |
| 167 | Cohort Retention Tables, Customer Happiness Reports, Traffic Referral Reports or Revenue Reports are typical examples for accounting reports. |
| 168 | it usually doesn’t matter too much if we have only little historic data |
| 169 | These insights usually lead to experiments (eg a/b tests). |
| 170 | it is very important to have historic data |
| 171 | data integrity is very important |
| 172 | This insights usually lead to strategic decisions. (eg switch sales focus) |
| 173 | The second axis i tend to look at is external and internal analytics. |
| 174 | External Analytics covers all public facing pages |
| 175 | Internal |
| 176 | reflect if your product provides value |
| 177 | Many product have a very clear distinction between external and internal |
| 178 | Sometimes it’s a bit blurry |
| 179 | GA is great for everything external |
| 180 | I am a huge Google Analytics geek |
| 181 | referral optimization |
| 182 | If you use GA for all external stuff you will be very happy. |
| 183 | GA doesn’t think in users and events |
| 184 | GA wasn’t made for product insights in first place |
| 185 | They think in “people” and “events”. |
| 186 | Mixpanel |
| 187 | product-internal exploration |
| 188 | product-internal |
| 189 | KISSMetrics |
| 190 | revenue tab |
| 191 | Most tools are integrated through push events. |
| 192 | Data Integrity |
| 193 | your integration will break |
| 194 | you will change how you track |
| 195 | Did you ever see different numbers in different tools? |
| 196 | Well that’s what i am speaking about. |
| 197 | In case of exploration this usually tends not to be a big problem. |
| 198 | In case of accounting this is a big problem. |
| 199 | Focus on product internal aspects |
| 200 | product-internal reports |
| 201 | tied to your product. |
| 202 | The more you need to zoom in - the better you work based on your own database. |
| 203 | performance problems |
| 204 | own server |
| 205 | Disclaimer |
| 206 | I advice you to segment your existing database data for reporting |
| 207 | If i can help you anyhow with your analytics setup - let me know |
| No | Text |
| 1 | complicated |
| 2 | complex |
| 3 | Why are those things sometimes great and sometimes horrible? |
| 4 | know how to decide |
| 5 | find what they need |
| 6 | implement a solution |
| 7 | old (3) |
| 8 | bad |
| 9 | previous |
| 10 | Example: |
| 11 | Why i wrote this post: |
| 12 | For those who don’t know me and just stumbled into this post by accident: I am @andreasklinger -among other things - I helped to build up Product Hunt as a fully distributed team. Btw&h****ip; yes, they are awesome, yes, they hire internationally, and yes, you should consider applying. |
| 13 | So here without further ado&h****ip; here&h****ip; we&h****ip; go. |
| 14 | Why does the distinction matter? |
| 15 | this is work |
| 16 | what |
| 17 | why |
| 18 | need (2) |
| 19 | TL;DR: |
| 20 | dummy mockup is dummy |
| 21 | “That’s the kind of advice gives someone who charges money for consulting? Make him draw complex graphs or bring the pitchforks.” |
| 22 | “But we need to track so many things” |
| 23 | Newsletter Submitted |
| 24 | Clicked Newsletter Submit Button |
| 25 | There are a few hard truth facts we need to accept: |
| 26 | When people speak of “product insights” they tend to mean that internal view of your product. |
External Link Count
: 112
| Icon | Domain | IP | Alexa Rank |
| Navnav.co | 66.6.44.4 |
304.063 | |
| Catscafecomics.com | 66.6.44.4 |
191.624 | |
| Egg.design | 66.6.44.4 |
1.237.038 | |
| f****inghomepage.com | 66.6.44.4 |
59.127 | |
| Hstyles.co.uk | 66.6.44.4 |
116.020 | |
| Rugbybabice.cz | 66.6.44.4 |
2.811.352 | |
| Mcmansionh****.com | 66.6.44.4 |
387.164 | |
| The-Utopian.org | 66.6.44.4 |
- | |
| Patternry.com | 66.6.44.4 |
2.022.838 | |
| Artandsciencejournal.com | 66.6.44.4 |
- | |
| Failedprojects.net | 66.6.44.4 |
- | |
| Nagaokaryosuke.com | 66.6.44.4 |
- | |
| Jenniferhaley.com | 66.6.44.4 |
- | |
| Robodino.org | 66.6.44.4 |
- | |
| Blakegopnik.com | 66.6.44.4 |
9.408.887 | |
| Letterheady.com | 66.6.44.4 |
7.160.478 | |
| Hondasmarthome.com | 66.6.44.4 |
- | |
| Blog.agavi.org | 66.6.44.4 |
- | |
| Georgianlondon.com | 66.6.44.4 |
- | |
| Toket.org | 66.6.44.4 |
- |