Skip to main content

Velosos 5Qs

We covered an interesting thing today on the Emarketing course. The general feel today was an introduction into writing persuasive content and how you engage the customer / reader on your website (although the same ideas apply off the web as well).

The main idea to get a customer interested in your products and services is engage in an internal conversation in their heads. The idea is to give them content that they can identify with, makes them think about themselves and what they want and need and then suggests a solution to them (ie: your product / service).

There is a person called Veloso I after a bit of digging I assume it it this Maria Veloso. They have 5 big questions that were pushed as a great framework to write content. We call them the 5qs!


  1. What's the problem? Identify the problem with the customer in the text, or explain a situation that helps them identify their own current problem.
    For example, you currently don't have all the sports channels on television so can't watch the premiership matches.

  2. Why hasn't this been solved before? The customer may not have thought about it, the price may never have been right or the product just wasn't advanced enough.
    For example, the customer is not in often enough on a saturday to watch the matches and often they want to watch 2 matches that are on at the same time so what's the point.


  3. What are the possibilites? How can they solve the newly identified problem.
    For exmaple they could get Sky Plus and Setanta Sports.

  4. What's different now? Make them imagine what it would be like with the product and the problem they had solved. Appeal to the right hand sidfe of the brain (the emotional side) so that they can make a decision that the problem needs to be fixed.
    They are now able to go out on a Saturday or stay in and watch the games, they can record the games if they are not there and still watch them later in the evening.

  5. What should happen next? This is where the introduction of your company and your services come in and you in clude a call to action to contact you or buy the product form the website.
    For example, if this was for Sky+ and Sky sports, the article could call them to contact Sky now and get the Sky+ box for free for a limited time now (incidentally they are currently doing this at the time of writing).
As I am writing this at the moment it feels a little bit airy fairy and cheesy. When I was on the course it didn't quite sound like this. I think it is important to follow these ideas, but in a more subliminal way. Ensure that you are identifying a problem, why it's a problem, what they could do with the problem solved and how you can help solve it. When you look at all good content on the web in general they are already doing this in one subliminal way or another.

I am still thinking how this can be applied to a software development company (which I work for). I think if we were selling e-commerce solutions then it is fairly easy: In relation to the 5 questions above I could outline the following:
  1. The customer doesn't currently have an e-commerce site so can't sell well on the web
  2. They have not done it before as they didn't have the expertise
  3. They could make a lot of money from selling on the web. In fact if they are selling a small niche product that is quickly becoming the best / only way
  4. Once it is set up they are getting lots of orders through, making plent yof money and the business is secure with less overheads
  5. My company is an expert development company that can set up the e-commerce site for them
The course is going well. I think I need to keep thinking about what as a company we want to sell to people and how can we package it up for them.

Comments

Popular posts from this blog

Creating star ratings in HTML and Javascript

I'd searched around a little for some shortcuts to help in doing this but I couldn't find anything satisfactory that included the ability to pull the rating off again for saving. I'd ended up coming up with this rather cheeky solution. Hopefully it helps you too! This is my first post in a while (I stopped blogging properly about 8 years ago!) It's strange coming back to it. Blogger feels very crusty and old by todays standards too.

Make your objects immutable by default

More about the Good Dojo In my post last week , I discussed creating objects that are instantiated safely. Please go back and read if you are interested. At the end of the post, I mentioned that I'd also written the class so it was immutable when instantiated. This is important!!! I feel like a broken record in repeating this but I am sure at the time of writing your code, you aren't modifying your object all over the place and so are safe in the belief that protecting against mutability is overkill. Please remember though, your code could be around for a hell of a long time. You aren't writing your code for now... you are writing for the next fool that comes along (including you) . Nothing is more upsetting that coming back to fix a bug on some wonderfully crafted code to say "Who has butchered my code?!", but often you were involved at the start of the process. You made the code easy to modify, allowing objects to be used / reused / modified without thi

An instantiated object should be "ok"

I've been QA'ing quite a bit of work recently and one common theme I've noticed across both Java and C# projects I have been looking at is that we occasionally open ourselves up unessacarily to Exceptions by the way objects are being created. My general rule of thumb (which I have seen mentioned in a Pluralsight video recently but also always re-iterate in various Robust Software talks I have done) is that you shouldn't be able to create an object and then call a method or access a property that then throws an exception. At worst, it should return null (I'm not going to moan about that now). I've created an example below. We have two Dojos, one is good and one is bad. The bad dojo looks very familiar though. It's a little class written in the style that seems often encouraged. In fact, many classes start life as something like this. Then as years go on, you and other colleagues add more features to the class and it's instantiation becomes a second