Skip to main content


Running an SME during #CoronaVirus...

Thought I'd share the philosophy and set of short term decisions we came up with at forgood. Feel free to copy/paste/steal whatever you feel is relevant. Tough times - but that's when humans are usually at their best. These were all crowdsourced and developed by the forgood team. Thanks to the team - we're only a few days in - but everyone is displaying emotional maturity, patience and humour. All that and more are critical to getting through this. Hope this content helps in some way. Stay safe out there 👊 Our Philosophy 1. Don’t panic. Get a flu shot. 2. We’re a small team - if someone gets sick - we’ve got your back. 3. Help our ecosystem wherever we can, given our fortunate position and ability to ride this out.  4. Keep moving forward! OKRs stay in place wherever possible - we just find new ways to get there and new ways to add value to clients. 5. Timescale. Plan in 2-4 week bursts. But understand this could last till October 2020 and beyo
Recent posts

Andy’s 10 Rules for Tech Businesses

I've been collecting these for years. The scars and triumphs of experience. Thought I'd share... #1 // Always get 5% better Revolutionary leaps happen from constant evolutionary pressure. Getting 100% better overnight is often impossible, but getting 5% better every day, week, month and year will lead to radical progress. #2 // Users can be idiots – but we love them anyway Users will always do what you don’t expect them to. They’ll click where you don’t want them to click. They’ll struggle with everything you think is simple – and breeze through everything you think is complicated. They'll have the system configuration or set of IT policies that you'v never encountered before. Remember, you’re building systems for THEM. They will always follow the path of least resistance. And without them, you don't have a product. #3 // Get shit done What gets done, deployed or delivered to a customer is infinitely more important than the process you took to get ther

The "Tour of Duty" approach to management and hiring...

This concept popped up on the Masters of Scale podcast and hasn’t gone away. It's been gnawing at me, mostly because it fits with a lot of my hiring experiences. With hindsight, this metaphor has gone a long way to explain why some staff stay, why some leave and what time commitment to expect from them. The best form of learning is writing - so here we go. A crash course in Tours of Duty. Let's start with the academic overview of the concept from Harvard Business Review . What is a "Tour of Duty"? It's a mapped out journey for both employee and employer. By setting expectations up front, you can manage the intergenerational conflict that occur between people who tend to stay in jobs for longer vs people who do a series of jobs for experience. It is an ethical contract, not a legal one - an undertaking by both parties of "what you want to get out of this". When you hire someone, the idea is to define their Tour of Duty with them - what is the

Open Source Startup: The Open Startup Movement

Welcome to Chapter 10 of Open Source Startup: The Open Startup Movement. This is the last chapter. For a table of contents, head over to the Introduction here .  Ever since I wrote the epitaph for Real Time Wine , I've been a strong supporter of more honest sharing in the South African startup landscape. There's a lot of ego floating around. Everyone is a CEO. Every CEO is a Rock Star. Until they fail, then they go away quietly. Failure is stigmatised - and the result of this is we have a skewed view of what constitutes success and more importantly, we can't learn from other attempts in our ecosystem. There's a movement in the US that may have particular relevance to our local ecosystem as we slowly grow up and de-stigmatise failure. Quoting here from a HackerNoon article ... "The Open Startup trend is a transparency and openness movement seemingly initiated by Buffer , quickly adopted by Ghost , capitalised by Baremetrics , and recently popularised in t

Open Source Startup: Codifying Company Culture

Welcome to Chapter 8 of Open Source Startup: Codifying Company Culture. For a table of contents, head over to the Introduction here .  Company culture. It's both the most frustrating, fluffy, intangible element of your business - and the thing that will sink you quicker than a bad VAT month. Startups are hard enough. Rather not spend your time with the wrong people following the wrong mission in the wrong way. Unfortunately, there is no silver bullet to culture besides talking about it. Choose a model, choose a template and talk about it. Then talk about it with every new employee. Then talk about it monthly. And keep talking. Here are a few tips and templates to get you started. Start with WHY . The famous Simon Sinek talk is a useful (and tough) process to go through. It forces you to think hard about why you're doing what you're doing. If you take the process seriously, it's also one of the best bullshit tests for a crappy vision or product. Understandin

Open Source Startup: Tools, Tools Everywhere and You Probably Only Need a Few

Welcome to Chapter 8 of Open Source Startup: Tools, Tools Everywhere and You Probably Only Need a Few. For a table of contents, head over to the Introduction here .  The tools required to build a startup, to test an idea, to get from 0 to 1 - are not as complex as you may think. In fact, it's quite easy to over-tool, to get carried away with the process rather than the outcome. Remember, there's a whole segment of startups just designing tools for other startups. Makes your head spin a little, doesn't it? Here's good introductory set of tools - useful for companies up until 10 team members. After that, you may want to relook at your toolset to ensure it scales with the team. Many of these will work, though. You're going to tempted to go for "everything free" - and I wouldn't blame you. But sometimes it's better just to pay. There is nothing more frustrating than spending time fixing your tools instead of building your business. Here we g

Open Source Startup: Disciplinary Policy Template

Welcome to Chapter 7 of Open Source Startup: Disciplinary Policy Template. For a table of contents, head over to the Introduction here .  Ah. South African Labour Law. We all know very well why it's as employee-friendly as it is. Because capitalism can be nasty and there are plenty of people that need to be protected. But it does make it quite hard to build a business in this beautiful country of ours. As a nation, we choose not to sacrifice protection of lower-income workers, therefore we need to figure this out and find a way to play the cards we've been dealt. The first step is to have an Employment Contract . The second is to have a Disciplinary Policy (which is specifically referenced in said employment contract) - and to make sure every employee of yours has received it and read it. A Disciplinary Policy is a safe guard against an enormous amount of time spent in the CCMA trying to get rid of a bad egg. And trust me, everyone is going to end up hiring a few bad