by Scott on July 02, 2008
I am done with “simple”. I say that even considering previous posts here about the virtues of simplicity, my enjoyment of books such as The Laws of Simplicity and Simplexity, and my respect for companies such as 37signals and Google (two companies commonly included in case studies on software simplicity). The word “simple” has several problems.
It is overused
‘Simple’ is a word that has become overused. You can take your pick from over 600,000 books on Amazon relating to ‘simple’. 64,000 in the business category alone. There’s over 46 million results for a Google search of “simple software”. In the CRM world, everyone seems to stake a claim to ‘simple CRM’.
It has no concise meaning
‘Simple’ is a word often used like ‘thing’. It is a good placeholder because it does not surprise people to see it and readers get some idea what you mean. But, like the word ‘thing’, ‘simple’ has too many definitions to provide concise meaning.
It has no impact
Instead of saying ‘simple’, let’s start saying what we really mean in a given context. Because it is overused and provides no concise meaning, you have nothing to lose and everything to gain by dropping it from a product’s vocabulary. Instead of a word the readers skip right over because they see it on millions of sites, use a word or phrase that accurately makes your point.
Replace simple with what you really mean
‘Simple’ is sometimes used out of laziness. It is the first word that comes to mind and it is harder to come up with different, descriptive words. Yet, I think it is worth the effort for the reasons mentioned above.
So, I went through the PlaybookIQ website and removed any mention of simple or simplicity that I could find. It was an interesting exercise because it made me really think about what we are trying to communicate. Depending on the context, ‘simple’ got replaced with ‘fast’, ‘easy’, ‘concise’, or with an entirely new wording. Readers now get a much better idea of the product’s power and the benefit of a given feature or design decision. As another example, the application I wrote to try out Google App Engine is called “lightweight” instead of simple crm.
Don’t throw out the concepts
There is great value in the concepts talked about under the topic of ‘simplicity’. I agree with most of those and we continue to look for ways to implement ideas under the topic of ‘simplicity’. Yet when it comes to describing any given idea, product or product improvement it is time to use words that are more descriptive and concise and less overused and vague.
[1]
comments
by Scott on June 30, 2008
Today we announce the launch of PlaybookIQ, offering a unique combination of small business CRM, plus process best practices. Much more powerful than general-purpose contact managers and address books, PlaybookIQ is built from the ground up for sales teams. Simply stated: PlaybookIQ shows you what was last said to a contact and automatically schedules what needs to happen next.
With PlaybookIQ, sales teams:
- Implement consistent and repeatable sales processes with Playbooks.
- Keep a complete record of all contact touchpoints with Contact Management, including automatic creation of comments with each step completed.
- See upcoming activities on the shared Calendar.
- See what needs to be done today on the Dashboard.
- Gain insight into progress and make sure nothing gets dropped with real-time Reports.
- Control who can do what with permissions management.
- Record contact data to your needs with custom fields.
- Collaborate among multiple users with flexible task assignment
- Include the whole team with affordable pricing.
Initial response and feedback from early users has been promising and very positive. With new features being released every couple of days, we are excited about this product launch and look forward to continued feedback.
To find out more about this new small business CRM and sales team collaboration software, visit these links.
You can email comments or questions to info@aboutplaybookiq.com.
[0]
comments
by Scott on June 08, 2008
Interested in an excuse to learn Python, and always on the lookout for production environments that are both stable and flexible, and I took a look at Google App Engine. To try it out, I created a simple contact and task manager that is live at http://bizz.appspot.com. I love the speed at which changes are deployed as well as the removal of environment maintenance tasks.
Python and Google’s webapp framework programming is rather straightforward too. I also find the constraints of Google App Engine really do steer me to keep things simple which leads to faster turn around time and less head-scratching.
With just a few hours of Python programming under my belt, I can see why Python programmers it as much as Ruby programmers enjoy Ruby. It really is an enjoyable language to work in and I’m looking forward to creating a couple more simple applications with Google App Engine.
[3]
comments
by Scott on May 28, 2008
Related to my previous post is this classic from Kathy Sierra, Be brave or go home. It’s worth a re-read now and then.
[0]
comments
by Scott on May 28, 2008
Two years ago I made the switch by buying a MacBook Pro for my primary development machine. Every day it seems I find another small reason to be glad to have switched.
Read more...
[3]
comments
