A good pointer from Pamela for anyone holding back from pulling the trigger
Another kind of micro approach – this one sponsored by one of the giants in the online world
Why twitter might not be such a bad thing – if a microISV uses it the right way.
How to game digg – or is that play the digg game?
programming methodologies ignore solo/2 person teams – here’s a rundown on applying Scrum to a microISV. Best I’ve heard of yet – but there’s more to be done here…
Tired of that dull headshot adorning your About page? Call in the artists! Cheap.
YouTube isn’t the only game in town – here’s 44 other ways of getting your screencast in front of your market.
Need a new exciting font for an key headline image? Here’s 40 really nice, usable ones from Smashing Mag.
Here’s a good starter list for making sure your microISV web site has the basics down in terms of ease of use: Scientific Web Design: 23 Actionable Lessons from Eye-Tracking Studies
Again, nothing startling in this list, but if your site is breaking any of these best-practices, you’d better have a good reason why.
Here’s the gist – see the post for why these are things you should be paying attention to.
1. Text attracts attention before graphics.
2. Initial eye movement focuses on the upper left corner of the page.
3. Users initially look at the top left and upper portion of the page before moving down and to the right.
4. Readers ignore banners.
5. Fancy formatting and fonts are ignored.
6. Show numbers as numerals.
7. Type size influences viewing behavior.
8. Users only look at a sub headline if it interests them.
9. People generally scan lower portions of the page.
10. Shorter paragraphs perform better than long ones.
11. One-column formats perform better in eye-fixation than multi-column formats.
12. Ads in the top and left portions of a page will receive the most eye fixation.
13. Ads placed next to the best content are seen more often.
14. Text ads were viewed mostly intently of all types tested.
15. Bigger images get more attention.
16. Clean, clear faces in images attract more eye fixation.
17. Headings draw the eye.
18. Users spend a lot of time looking at buttons and menus.
19. Lists hold reader attention longer.
20. Large blocks of text are avoided.
21. Formatting can draw attention.
22. White space is good.
23. Navigation tools work better when placed at the top of the page.
by Dan Schawbel
Who said that developers can’t be entrepreneurs? Well in a web 2.0, they are given the chance and opportunity to be that CEO. In a web 1.0 world, developers were slaves to corporations enlisting their services to sell products to customers, become profitable and then update those same products for the next revision. In the new age, everyone is one the same planes, hierarchies will soon vanish and guess what, you are a CEO. As the CEO of a brand called you, you are empowered to make a difference, start your own company, on any topic, blog, and perhaps, change the world!
Personal branding is a term defined as “the process by which we differentiate ourselves by identifying and articulating our unique value proposition to achieve a specific goal.” Our brand is what others think of us when they hear our names, its how we are perceived and what makes us stand out from everyone else. Those who sit back and don’t use the personal branding practice will turn into commodities. As a developer, it’s your chance to craft new technologies that can be implemented online and by doing so you become more visible, credible and famous.
Through blogging and social networking, developers have the resources readily available to them to start building a business. If you don’t have the business skills or the capital to start you business or fund your software projects, then you can pick and choose from your communities to fill positions. How do you know who is qualified? You know from the comments, the content and their biography, if they have the necessary skills to help you on your project.
Developers have the technical know-how to create the most impressive programs available and if that knowledge is paired with a businessman, then there is potential for an all-star team. I’ve seen this happen a lot on the web and sometimes the developer is also the businessman, such as Michael Arrington of TechCrunch. Whether it be a brand new social network (there are far too many as is) or a new application for business use, developers have more choices than ever and can freely connect with individuals online. To be an entrepreneur it now requires less money, but more people and great ideas.
Dan is the lead personal branding expert for generation-y. He commands the world famous Personal Branding Blog, publishes Personal Branding Magazine, directs Personal Branding TV, and is the head judge for the 2008 Personal Brand Awards
I caught the kick off conference call of the Personal Branding Summit this morning and I’m glad I recommended it here yesterday: some really good insightful discussion about building a brand for individuals and small companies.
Best quote of the session in my opinion goes to Andy Sernovitz: “Without a brand, you have to sell yourself twice.” So true! First you have to establish some credibility and authority and then, and only then, can you persuade your microISV customers to consider your product or service.
By blogging, by participating in or even building an online community, by commenting on blogs, by doing white papers, speaking at conferences within your industry, you build a brand. What brand marketing are you doing?
The Branding Summit is ongoing today (Thursday), and it’s free.
Here’s another (select) microISV blog to add to your reader: Software by Rob. Rob Walling is both a .NET microISVer (DotNetInvoice) and a consultant (The Numa Group), so he gets both how hard it is currently to bootstrap a startup and do software development.
Now if I can only get him share where he go the snazzy About image he uses!
Branding is something microISVs should know a lot more about. My friend Pamela Slim (Escape from Cubicle Nation) just clued me in on what sounds like a great free resource for microISVs:
My buddy Jason Alba from JibberJobber has organized a pretty cool free learning event tomorrow, entitled Personal Branding Summit. Details are here. It includes some of my favorite marketing and career types like Guy Kawasaki, John Jantsch, Krishna De, Richard Bolles, Phil Gerbyshak and Debbie Weil. Sign up for individual sessions that cover all kinds of personal branding and marketing topics.You can’t beat this line up for free.
Check out the sessions here – here’s a smattering that got my attention:
- Evangelizing Evangelists to Build a Business and Build Your Brand – Panel: Guy Kawasaki (facilitator), Krishna De, John Jantsch, Andy Sernovitz, Tim Demello
- Success Built to Last – Secrets from the most successful people on earth! – Stewart Emery
- How A Book Becomes A Brand: The 35-Year History of WHAT COLOR IS YOUR PARACHUTE? -Richard Nelson Bolles
- Three Steps to a Winning Brand – William Arruda.
[tags]Branding, Branding Summit[/tags]
A programmer friend of mine emailed me a few days ago with a frustration I’ve heard often:
The projects I can think of working on are rather generic (and
probably the low-hanging fruits): File backup/restore, information
storage/retrieval, money management… I can’t seem to figure out how
to find more “niche” problems.
What can I do to find them?
I mulled this over earlier this week while at the Business of Software Conference, listening to some really sharp people talk about different and interesting ways of looking at this business we are in.
Here’s what I came up with:
(Problem / Market ) * (Passion + Disruption) = microISV app.
Problem – This is something that causes a non-programmer pain. Note I said non-programmers. Programmers are not normal people and don’t see the world the way they do. First off, we actually like tech – they do not, unless their friends like it and it’s now been made cool and safe (think iPod and iPhone). Second, we think binary – either this class works or it doesn’t: They do not.
Market – These are the people who have the problem and are ready, willing and able to change. You can’t sell shoes to a man unable to walk and you can’t sell without a 24 month sales cycle, round 2 VC money and a direct sales force an enterprise software system to a HR department already locked into a system.
People are busy and have lots of problems. When problems hurt enough, when the pain, frustration, emotional hurt or self-image damage is enough, that’s when and only when they go to Google looking for a solution.
This relationship between Problem and Market means you need to find a sufficiently painful problem to enough people ready willing and able to change what they are doing now for you to succeed.
Let’s look at the lower half of the equation.
Passion – That’s what you need to have for the Problem. Since you’re not going to get paid (yet) for creating this app to address the Problem, you are going to need a large supply of Passion. Some people for various reasons find money generates passion. Most need something more – like liking the people who have the Problem, wanting to prove to themselves and the world they can write great software. Negative emotions can tank up your Passion tank too – Anger at some dumbass company that sells you something you know could and should be better; Frustration when you are part of that market.
Whatever floats your boat – just keep in mind you’re going to need a lot of it and no matter how horrendous the problem, no matter how large the market, you have to be sold on it first, it has to be something you feel a burning need to do something about. This is a pretty high bar to jump, and why hundreds of millions of people can know about a problem (Darfur comes to mind), but only hundreds will feel the absolute imperative to do something about it.
Finally there’s Disruption. This is the secret weapon in the secret formula. Because we’re programmers we can create tools to solve problems that are not 10% better, but 100 times better. We can disrupt – taking how people did things (the Problem) and recast it in an entirely different way.
Pick 10 apps or web sites you think are really successful. How many of them built their success on disrupting the way things were done before they came along? Every single one of them.
Disruption – called innovation by the suits – is what has driven technology for some 203 years since some bloke mounted a steam engine on a set of wheels running on metal rails and upset the established order.
MicroISVs have the incredible advantage of not having to produce n+1 apps. We are in the disruption business – and very happy to be so.
So when you are mulling what app or web service you should build your microISV around, go find someone’s apple cart to turn over, go find a problem that needs a heathy dose of disruption that gets you excited and energized – that’s the app you should write.
By Starr Horne
Every so often someone in the Business of Software forum asks about process.
For most mISVs, formal methodologies like extreme programming are extreme overkill. But there are a few “processes” that I’ve found essential to my business productivity.
Keep in mind – process is fundamentally different for a one-person company than for a large corporation:
- IT is no longer a separate department: So you need to address business as well as technical issues.
- You have the flexibility that larger companies would kill for. Process should structure your work, without sacrificing your ability to make quick decisions.
- Process should be biased toward action, not documentation. (Those TPS reports can wait)
Using these criteria, I’ve come up with four practices that have boosted my productivity and helped me hold on to a little bit of my sanity.
Hold weekly business and technical reviews
When you’re starting a business on your own, it can be hard to see the big picture. Why not devote two hours a week to self-review? Sit down with a pad and a big cup of coffee and ask yourself: What have I done right? What have I done wrong? How do I do better?
Define clear end-points
One of the hardest things about development is knowing when to stop. But there’s a simple solution. Create a “bare minimum” requirements document. As soon as you code and test a feature, check it off and move on! Don’t optimize, beautify or abstract. It can take real discipline, but you’ll be amazed at how much you can get done.
Create a work schedule (and stick to it)
There are a million things you have to do to create a successful company. It can be especially overwhelming if, like so many of us, you’re working full time & creating your ISV on the side. So do yourself a favor and make a work schedule. It takes the pressure off to be able to say “Hey, it’s GUI Thursday, I don’t have to worry about PR.”
Keep a “Not Now” list
When you’re racing towards version 1, you don’t have any time to waste. Every time you sit down to code a new feature, ask yourself: “If I leave this out, will it break my product?” If the answer is no, it goes on the “Not Now” list. This will save time, sure. But more importantly, it will train you to constantly focus on your core values.
If you decide to implement any of these techniques, or if you’d like to share some of your own, let me know! I’d love to hear them.
Starr Horne is currently developing the StepLively Switchboard, a CRM system for e-commerce, which incorporates live chat, email and click-to-call. You can read more articles by Starr in his development blog, The Startup Lowdown, and in his e-commerce blog LetsTalkEcommerce.com.
[tags]47hats, development, StepLively[/tags]