Saturday, November 26, 2005

a few things

A tick

I'd like to share something with you.

Every once in a while, I sit down and consider where I currently am, and how I got here. This time, I decided to make a list, and thought "hey, maybe I should share this list, someone might find it useful". And so I put together the things that I've been fortunate enough to learn about business during this last year.

A little background: About 4 years ago, three young guys fresh out of university decided to start an IT business. They did it without any funding of any kind, and with only one client. They were nuts…

I was one of those guys, and I smiled ever so slightly when I heard that we did our second seven-digit year a few days ago. I didn't smile too broadly, because it's only a start, but this is what I've learnt so far:



Lesson 1: Commodity markets are for big players

You can't build a successful business from scratch on the back of selling commodities. OK, not totally true, you can if you have access to large amounts of capital, but then you're technically a big player. Running a small business? Drop the commodities, and get into the business of specialisation in areas where you can distinguish yourself - there will be plenty of time later on to exploit large commodity markets.

We started out selling all sorts of IT stuff as a "reseller": PCs, networking infrastructure, etc etc. Then we realised that most "resellers" are actually redundant in the supply-chain, and that in an ideal market situation, they wouldn't be there, end-users would be buying directly from manufacturers (or their distributors, who can buy in bulk). Yes, you heard me: 99% of all small "IT solution providers" that focus on selling, repairing and upgrading hardware & software, installing networks etc are redundant. The only small businesses that can prosper long-term are those that specialise in areas that aren't commodity-based (like businesses that build just websites).



Lesson 2: Scalability is king

Some people struggle to make a living. Others, like doctors and lawyers, earn pretty decent incomes for themselves. Unfortunately, their incomes have ceilings. Get rid of the ceiling: if you want to accumulate true wealth, you need to distance yourself from the notion that you need to work for every cent that you earn.

Scalability, in principle, is a relative concept. Trading in products is scalable to some extent - if you hire more salespeople, you can reach more customers, churn more revenue, build capacity, and hire even more salespeople (or spend more money and smarts on reaching more customers in other ways). This kind of scalability is limited though… Sure, you reach economies of scale at some point, which enable you to earn more revenue relative to your input than you did at a previous stage, but you still need to input more. I like exponential scalability more...

Serving 10 000 customers with only a fraction more effort than it takes you to serve 10 customers? That's scalability, and one of the best ways to make serious money.

Lesson 2.1: Don't scale before you need to

Building a scalable system with the assumption that you'll only get a return on it once you have the huge numbers you're aiming for is not always wise. Here's what I suggest: Very carefully consider what will be needed at a large scale, keep it in mind, and then build a smaller version of it first. Don't over-expend if you don't need it yet.



Lesson 3: Sweat procedures, it's worth it

Open-source advocates and start-up types hate policies and procedures. They say it kills spirit, that it's part of corporate bloat. Sometimes, maybe, but it's also a crucial enabler of scalability. If you only have smart, post-graduate geniuses working for your business, you might not need procedures. Unfortunately, businesses that only have geniuses working for them aren't all that scalable. You need people to run the market-facing systems that your geniuses create for you, and those people need procedures, otherwise the business can't be efficient, and things very quickly fall apart.

As my one partner once said:

Post-optimisation is the mother of all f#$&-ups.
Pre-optimise with well-planned procedures, it's worth it.



Lesson 4: BECOME the customer

A while ago, Jennifer discussed getting closer to customers by talking to them.

Sure, not a bad idea, but it's even better actually becoming the customer for a while. I did it a few times this year, even getting into arguments with my guys about features that I wanted in our products (both the scalable and non-scalable ones). We sat down and looked at both sides, added things that were worthwhile to add, and explained to our customers why we weren't adding things that weren't.



Lesson 5: Specialize, and then share

Don't be scared of letting go of things that other people are better at. Partner up, let other businesses do the things they're good at - and then focus on doing the things you're good at.

I've seen it so many times: businesses who are scared of losing income if they don't offer everything their customers want. Sure, there's always a case for complimentary services, and one should generally consider each situation, but don't be silly. If you know someone else is better at it, let them do it. We're Microsoft Partners (and I believe one of the smarter ones in the Western Cape), and we specifically point out to other partners that we're not competing with them - we show them what we do (generally, very few others are good at these things), and then mention that we gladly partner up with them when our clients need things that they're good at. Microsoft encourages this in their partner channel, and I agree with them.



Lesson 6: Rock stars get the chicks

It's one of those things. Perception rules the world, and this is only a bad thing if you don't know how to manage perception.

OneNote is 500% more kick-ass than Backpack, but Backpack gets the BusinessWeek article and rave reviews. Why? Because Jason Fried is a rock star.

Next year, watch out for a new band in the world of the Information Worker and scalable web services. Rock on.



And, finally,



Lesson 7: Commitment commands respect

People are strange things. They easily get caught up in hype, emotion & social habits. Businesses are built on people. Thus they're vulnerable to the instabilities of people, but also to the strengths of these same people.

Leadership can't be taught. It evolves. Management theory makes up 2% of what's needed to create and maintain vision and motivation within an organization. The rest is determined by gut feel, experience, and commitment. Commitment in the form of a never-say-die attitude, in exemplary dedication to the task at hand, in practical things like forsaking sleep for 24 hours to resolve a crisis, in taking a pay cut, in truly caring about a better future enough to drop everything else to make it happen.

Respect - earn it through commitment.

That's it. 2006 is going to be a sweet year.

Imagined on Saturday, November 26, 2005

Comments [21]

Categorised as


 Saturday, November 12, 2005

oh, the memories...

Last year, Onanymous won all our hearts with her Do you remember post.

This afternoon, I came across an amazing collection of sound clip links which gave me that warm fuzzy South African feeling all over again - Remember Wielie Walie, Derrick, Vyfster and Agter Elke Man? Die Man van Staal? Trompie?

Pumamouse, thank you - I feel like I'm 5 again… :-)

Imagined on Saturday, November 12, 2005

Comments [23]

Categorised as


 Wednesday, November 09, 2005

rundle is a genius

I wanted to say it a few days ago, after the 9rules re-launch, but I got too busy. Then, catching up, I checked out his latest work, a redesign of Om Malik's blog, so now I'll say it:

Mike Rundle is a genius.

Seriously, the guy knows how to design interfaces. He's a craftsman at the highest level. The redesigned 9rules homepage is IMHO the best example of what Microsoft should be doing with Windows Live's interface, and where the Live Web (I hate that "other" term) in general should be heading. Credit is due to Colin also, naturally.

Respect.

Imagined on Wednesday, November 09, 2005

Comments [11]

Categorised as  | 


 Tuesday, November 08, 2005

centrino kicks ass

MSI Megabook M510C

3 months ago I decided to up the ante and get myself a top-of-the-line notebook. My partners had both been raving about their MSI Megabooks, but I did some research before buying anyway, just to be sure.

It turned out that the M510c was the highest spec machine I could get, and the pricing was very good (mainly because it was at the time the only laptop one could buy in SA without a Windows OEM licence - because we're MS Partners, we already have plenty of those). And so I ordered mine with a Centrino 1.7Ghz (2MB L2 Cache), 1GB RAM, and an 80GB (8MB cache) Western Digital drive…

Fast forward to this morning.

I'm sitting here running the following simultaneously:

  • Outlook 2003, with blueFIRE
  • CorelDraw 12, with a large layout doc open
  • CorelPhoto-Paint 12, with about 10 screenshot PNGs open
  • Flash 2004, with a short 30-second demo-movie open
  • Two virtual PCs (yes, actual, networked machines running)
    • Windows Server 2003, with Exchange 2003 and SQL Server 2000
    • Windows XP with Office 2003, connected to the server above
  • Visual Studio 2005, Web Developer edition, with 8 files open
  • OneNote 2003 running on my second monitor
  • Firefox (6 tabs open)
  • Internet Explorer
  • Windows Explorer in some directory
  • Winamp 2.91 (I refuse to switch from perfection)

Holy crap. Yes, a little bit slow since the XP virtual machine started up, but c'mon...

Three words: Centrino. kicks. ass.

Imagined on Tuesday, November 08, 2005

Comments [14]

Categorised as


 Thursday, November 03, 2005

high-impact design

Web design is an easy thing. Actually, graphic design (broadly speaking) in general is a pretty easy thing - compared to, for example, missile guidance system development - which is why most designers try to make it seem difficult. Hell, they don't just make it seem difficult, they actually make it difficult (for themselves, inevitably).

Settle down, I'm not throwing mud pies at web designers. At least not the ones that kick my ass without any contest.

Instead, I thought about an interesting concept yesterday:

High-impact design

Hear me out: It's design that forgets about the details, breaks things down to the core, and keeps it at that. Because of this lack of complexity, it's design that can be planned, executed and implemented within a fraction of conventional timeframes. The effect is that it becomes design which is much more viable economically - it's profitable.

The new blueFIRE site is my attempt at high-impact design, and what got me thinking about the concept. I conceptualised, planned and put together the site in 3.5 days, using extremely simple CSS and as little coding as I could. Yes, the Flash took up most of the time, but it adds to the impact.

Quite frankly, I think that most designers spend too much time tweaking details on projects with positively finite lifespans. I mean, c'mon, most webpages (if they're relevant) shouldn't last longer than 2 years. Spending an inordinate amount of time on short-lifespan stuff just doesn't make sense. Sure, I appreciate beauty as much as the next person, but it doesn't always make sense economically. If it does (such as with extremely high traffic sites), then by all means spend the extra time - however, how many of us build an MLB.com every day?

Free your resources, free your time - when you can, design high-impact.

Imagined on Thursday, November 03, 2005

Comments [3]

Categorised as  |