Brain Breach

As a dedicated software adventurer, Chandler has been on my radar for a very long time.  Since 1.0 came out today, I thought I might give it a go.

What Chandler is: a project that hopes to sync with great services (gmail, outlook, etc) and is therefore quite welcome.

What Chandler is not: functional or useful

Ouch!  I am quite sorry to give such a review of this project.  I know what it takes to pull something like this off, and how much Mitch Kapor’s heart has been poured into it.  Let’s hope this isn’t a pattern for later releases of Chandler.

Four Reasons why Chandler 1.0 is found wanting

1. It doesn’t do anything that I need

Sure, it syncs my to-do’s and calendar with other stuff, but does that matter when the to-do’s aren’t useful, and calendar has nothing new to offer?  In other words, who wants to sync something they don’t really don’t need? Sync a mess at home, and it will appear at work also!

2. Tasks are a mess

Chandler is supposed to follow the GTD paradigm.  The problem is it just uses the most minimal implementation possible.  So if you want to mark something beyond just now/later/done, you have to schedule it on the calendar.  This poses a few problems. Mainly, there is no abstraction, which is really the heart of GTD, i.e. “don’t stress over that now, you can only do one thing at a time”.

Thankfully, they do have “note”(the universal item in Chandler) categories. You can’t even drag/arrange tasks.  Their idea of abstraction is a star. Your note can have it, or not.  Well, after you mark a dozen of those, they start to loose their meaning.

With so much competition in the tasking arena, Chandler is certainly nothing to get excited about.

3. No contacts

Really, this program wants to be a PIM (personal information manager).  It’s my opinion that nothing is really going to take over this market until they take a truly SMART comprehensive view of PIM. There have been many brave attempts, but since there is a large gap between great ideas and solid implementation, we probably have to wait for a couple more years before something killer comes along.

So how are you supposed to link a to-do to a contact to a calendar entry?  You can’t right now.  I bet you a nickel it’s in their plans, but that doesn’t help us today.

4.  Memory Muncher

The Python runtime jumped to 140 mb after some very average usage in Chandler. Python has its own memory management, but how well will it do under heavy usage?  Remember Python on the desktop isn’t a terribly popular scenario, and Chandler could find themselves with low level programming they aren’t ready to handle.  But, that is a risk I bet they have wagered well.  You have to take risks to move ahead in the tech world.

Really, I do hate to be so down on fellow entrepreneurs and developers.  Truly, I wish them the best.  Please, own this category! Until then, I am sticking with ToDoList and a medley of other apps.  My prediction is that Google will be the first to confront the ugly monster that is PIM with poise.

+ update : I found Thinking Rock, and so far, I really love it. It will probably take the place of ToDoList.

Having experience playing important roles in a couple business, I found myself quite familiar with many ares of business. One area I hadn’t researched was sales. How does one become a respectable salesman? After spending an hour in Barnes and Noble’s business section, I picked up Exception Selling. Certainly, I am not proposing I lead this area in my company, but until the resources justify a sales team, here we go.

The following are some of my notes on the adventure. I recommend this book, but I don’t know what that’s worth to you, being my first book on sales.

Exceptional selling, notes

Pages 1-50

• when you are feeling pressure, you are doing something wrong
• never answer unasked questions

• just making a value proposition makes customers see your service as a commodity. Then they make a decision based just on price.

• don’t be a lecturer, It’s a ineffective way for them to learn.
• stop persuading and start collaborating

• don’t come in thinking you are a salesman, but a trusted advisory

• value proposition is not enough, everyone offers that.

• value gap, the gap between what you think it’s worth, and what customers do. crossing this gap is done by offer the customer value as they see it in their world

Sales life cycle

value proposition – tell them what you do

value assumption/premise – something you both agree could be a value to them, and MIGHT be confirmed after further investigation.

value absent – investigate the consequences of absent value, quantify, and show

value required – the customer acknowledges value is required

value expected – where you confirm exactly what can be done, for how much

value achieved

Pages 50 – 100

• diagnosis mindset is opposite from presentation mindset.

• you diagnose WITH the customer. selling is something you do TO them(bad)

• go for the ‘no’ early and often. make sure they are ready for what you offer, and if they aren’t, move on quickly to qualified sales leads

• diagnose the problems without insinuating they are incompetent

Mindset

– change guidance
– mutual self respect
– don’t let them run over you
– emotional maturity
– you must remain emotionally detached, but professional in tune

• the process,
  discuss, diagnose, design, deliver,
  the following is the application of those.

• be prepared , and research the company/person you are calling.

• people won’t reject you if you aren’t being a salesman.

• the first call should be one of discovering the problems, from the people closest to the action. – Questions like: do you see this happen? What are the results? – Ask for facts and consequences, – don’t talk about yourself for more than a few seconds

• discovery conversations are not sales calls

• cold call script, pg 92
• towards discovery stage script, pg 97

• don’t answer with questions
• When getting customer is digging to deep before you have appropriate information, keep answers to 20 seconds, and continue where you left off.
• The questions will be; how much and how long, etc. Answer, and get back to learning about them.

• give the customer a small assignment, it keeps them engaged and conjures a sense of collaboration

• high probability to close sale when they learn they have great need

Pages 100 – 220

• once you have permission to move on, start the diagnosis.

• this phase is about thinking of their situation, not your solution

• never let the customer self diagnose, you have the domain expertise

Diagnostic conversation model

– what is happening
– why is it, how bad
– is it bad enough to act on?

• don’t use insulting questions when exploring what they said. neutral ones like ‘can you help me understand ‘not fast enough’’ ?

• questions should start with asking observations, not accusations.

• never insult competition, acknowledge them.

• ask what methods they have used already to fix the problem. don’t assume they haven’t tried.

• let the customers co-create the solution with you, this way, you get a better solution for them, and they gain more trust with customer.

• ask questions from customer point of view; ‘when would you like to see this solution up and running?’, not ‘when can you make a decision?’.

• actually, that’s wrong wording by Thull, again. more like, ask questions from a customer value position, not a sales value one.

Proposals – a confirmation on what has already been decided

1. No surprises
2. Us their wording/phrases wherever you can

• don’t skip diagnosis even if they think they have a problem. they don’t know the value of fixing it until you lay it out for them.

• if you can’t put a cost to the problem, you don’t have a problem

Financial conversation

– how much does our absence cost them?
– What return can they expect from solution?
– How much is that worth to them?

• it’s critical that company execs take part on the sales team when talking to other execs. they have the experience and depth of knowledge regarding their value