This post is part of a series, a diary of starting a business if you will. It follows part 1, the decision of becoming an entrepreneur.
One thing I found out is that it’s hard to put your responsibilities down on paper… there are so many!!! There is of course a basic job-description, which more or less sounds like that of a project manager/pull-the-rabbit-out-of-the-hat magician: “make it happen that we go from this thing on paper to the product in the hands of customers.” “Make it happen” is a super-loaded phrase, which can mean countless things.
There is a continuous struggle between micro-management and keeping the overview. Micro, because it is your responsibility that every (little) thing is carried out by your employees (if you have them). Overview, because You the entrepreneur are The Organisation. There is a third struggle that shouldn’t exist really, that between your professional life and your personal life. I’ve come to the conclusion that the only way to do this thing well is to focus on it exclusively. Friends, family, love, …blogging… it’s a nice luxury to have, but it comes second place.
The responsibility of an entrepreneur are thus: have a goal and make sure that everything is executed to get to that goal.
In a technology company, there are matters of technology and business (really, in what business except for strategy consulting isn’t there a mix of “technology,” which can mean anything from cooking to software development, and the commercial side of things, which is meant to pay for everything?). What I found was that as someone with a business background, who sort-of-kind-of has an idea about product development, and has a better grasp of business development, I still can’t let go of the reigns of product development entirely.
Product development ties in directly with business development. People are unwilling to pay for something that doesn’t exist and similarly our budget is supposed to last us until we have something worth paying for or investing in. Therefore, as an entrepreneur I have to make sure that product development stays on track. The absolute best way to do this is to have a capable product development manager in charge. The truth of it is that startups by their nature are resource-poor, which includes tripple-A product development managers (probably employed at multinational X or Y somewhere), and there is a lot of learning/training on the job. Learning/training means that the (hopefully) existing product development manager (in our case yes) still has to be managed, through schedules and regular meetings. In any case, product development is in its conceptual stage a very brainstorm-friendly activity, which means the more the merrier. But ultimately, a startup must get beyond this stage, respecting the entire resource-poor situation that a startup usually faces.
So, responsibilities of an entrepreneur as far as the technological product development is concerned: If you have a product development manager, you have to make sure that he works under the realities of the business. If you don’t, which I imagine many 1-person software startups operate under (as well as those lucky strategy consultants), well then you have to do the job of product development as well, keeping a close eye on the business realities.
OK, the business part of things. My role is fairly well-defined here as I come from a business background and approach startups from a business perspective. Assume that role 101 is having a firm grasp on everything that goes on, which can be phrased as “where are resources (people, time, money) being expended at and is it wise to do so.” This entails having a good budget plan and sticking to that.
Role 102 is to build the business, which I call business development, but that often gets confused with sales as that that is what it says in job adverts. Business development is the building of the business, which includes sales, but also includes building the company and all that entails.
So, we are trying to get from point A to point P, how do we go about it? If product development is about turning an idea into a product, business development is building a business plan into a business. Business plans are total BS unless they contain validated information. Some key-chapters in business plans are the market overview, the market approach, the time-line, and the financial need to meet all these objectives. Business plans can serve as a. cannon fodder, b. a plan of approach, c. one of several signals to attract investment. For c. no investor will take a look at your business unless you have a plan of approach (b.). On that plan, there should be a time-line, which you are following (predictability!) and there should be a goal: the market you are targeting and your approach.
The market section of the business plan presents a big problem for technology entrepreneurs. Because (non!) customers often don’t know what they want. I can ask a target group “what kind of air do you like to breathe?” and it wouldn’t surprise me if a significant number of responses would say: “I like to breathe air that smells like perfume.” OK, that’s a terrible question, but what I mean is that people sometimes make up answers that have nothing to do with reality (that said, both the perfume business and the fast-food industry have made lots of money from essentially selling air that smells good. Scent is also plays a very important part in memory, but I digress…)
What I’m a big fan of is validated market data, which is data gathered from actual customer experience with your product or part of it. That brings forth another problem of a bias towards early (and over-excited) adopters, something which the book “crossing the chasm” deals with, but is really not something that I think is realistic to address at an early stage, except that validated market data can also come from experts in the markets you are targeting.
The implication is also that product development is again completely tied in with business development which leads us down the path of rapid prototyping, another practice that works great in software / on the web, not as easily (though not impossible) with hardware. In any case, the experts in this area most well-known today are:
- - Steve Blank, who wrote “The Four Steps to Epiphany” and is currently hosting the excellent Stanford’s Entrepreneurial Thought Leaders seminars (btw. Steve Blank also writes a great blog on customer-focussed development, which I’ve only just started reading.
- - Eric Ries, who authors the blog Startup Lessons Learned and has some great articles on responsible (=lean) development.
- - And Donald Reinertsen, who wrote an incredibly dense book called “Principles of Product Development Flow,” a book which is clearly an authority in the field, but which I cannot recommend to any sensible entrepreneur with a 60hr/week schedule. Those principles, by the by, number in the 100+.
As well as of course Toyota and plenty of other experts out there, I’m sure, many of which are referenced by the people mentioned.
I think that it can safely be said that task 3 or a sub-task of business development is working towards the customer, the lifeblood of a business.
There are other tasks of course, which have to do with human resources, legal work, accounting, etc. Some of which can be outsourced, some of which can be done half-heartedly (oh no, I didn’t say that), some of which are really-really important, etc.
All these tasks, however, require a certain authority. The entrepreneur’s responsibility is to either be an authority on a task level or to be sure to work with authorities, either in the company or in an (informal) consulting fashion, so that they are carried out responsibly.
Task 4 can thus be entitled: be an authority on the tasks that need to be carried out or have access to one.
So, a whole can of worms starting a company can be and it is vital that it does not interfere with the single most important thing that you must do as a human being: be healthy! Health is part sleep, part exercise, part food, part love. There is no yin without yang and vice versa. Thus forget everything I said about personal life being no. 2. The best is if it reinforces what you do in your work. Health leads to happiness and happiness leads to optimism: a key-quality in entrepreneurship if there ever was one.
So the responsibilities of an entrepreneur summarised:
- 100: keep your eye on both sides of the court: the goal & the resources needed to get to that goal
- 101: align Product development with Business development
- 102: always validate your market data by staying close to your customers
- 103: be an authority on the tasks that need carrying out or have access to one
- 104: stay healthy and happy.
This was written in a single session with minimal editing. I hope it kind of makes sense. Part 3 of my e’diary will be on the topic of: can you prepare for entrepreneurship? As I have a master in entrepreneurship, I thought it might make for an interesting perspective. All my entrepreneurial diary posts can be followed under the tag ‘Vincent’s eDiary.’ By choice, I’m being mysterious about my company. If you have questions, feel free to comment or write to me via the email address on the right.
Picture courtesy of Be The Dream.

Like
Unlike