Focus focus focus

I’m a big fan of things that kick ass therefore I’m a big fan of focus.

In almost anything you do, more focus is better. Try to get as focused as you can on doing something really really well. This is pretty hard when you’re talking about yourself, but easier when you’re talking about a company, and much easier when you’re talking about designing an application.

By focusing on one thing, you can really make it awesome. Don’t think Minimum Viable Product. Think Minimum Lovable Product. You want your customers to love your product. That’s rarely accomplished through additional features – it’s accomplished through one key feature, perfectly executed.

When you’re entering a competitive market, it’s unlikely you’ll be able to do everything better than the established players. By focusing on doing one thing much better, you can clearly differentiate.

You have limited time and resources to get a product to market. You want it to market as fast as possible, for as cheap as possible. This is the idea behind the MVP: building less means spending less. But, leave some time in for polishing. Never launch with something that’s not polished: you want to be known for quality not crap. You’ll be tempted to use that extra time to add more features or change it around, but don’t!

Building a brand is like getting fit

Everyone wants to be fit, but few are willing to put in the work.

Over the past decade, I’ve spent a lot of time working out and talking with renowned trainer Nate Miyake. We talk about a variety of stuff, but often end up in the same spot: doing anything well takes time, effort, and discipline.

If you want to get fit, you don’t just wake up one day and decide that today you’ll get fit. Sure, you can buy some Spanx, but they’ll only take you so far. Instead, you have to set goals that work for you, and make the small decisions everyday that help you achieve those goals.

It’s the same thing with branding.

Many times, I’ve spoken to people who think building a brand is just a matter of hiring someone to give them a logo. That’s like buying Spanx – it’s a temporary, uncomfortable solution, and won’t stand up to scrutiny.

Instead, building a brand is a long term process, which requires careful planning and goal setting, plenty of preparation, and ongoing discipline and action.

You don’t get fit by walking into the gym one day, randomly lifting a few weights using poor form, and walking slowly on a treadmill for 15 minutes. But that’s what many people think with regard to their brand.

So how do you get fit?

  1. Set goals that are personally resonant and realistic. Do you want to run a marathon, climb a mountain, or just get to a reasonable level of fitness?
  2. Develop a strategy that includes overall diet and workout plans.
  3. Prepare by getting the things together that you’ll need. This may include things like buying running shoes, workout gear, and getting a gym membership.
  4. Execute! This is the easy part, but also the hardest part. There are no short cuts, no secrets. It’s just discipline and hard work.

This is similar to branding:

  1. Define who you want to be in a way that’s resonant with employees and realistic. In some ways, this the hardest part – and the most valuable part – of the entire process.
  2. Develop the foundations for building that – how you’ll look and how you’ll talk about it. Develop a plan for getting it out there.
  3. Prepare to meet the world by extending it to different mediums – your website, videos, etc.
  4. Execute! This is beyond simply making things look good. This means following up on the decisions everyday that reinforce who you said you’d be.

When it comes to getting fit, most people tend to prefer to skip to step three and stop there: I’ll go by a pair of running shoes – that’ll do it! In the same way, many companies prefer to skip to step three of branding and stop there: we need a new website, and that’ll change our brand! And it doesn’t, and they wonder why.

Some useful tools

Here are some useful tools:

http://fakeapp.com/ – for automated testing

http://peacockmedia.co.uk/integrity/ – broken link testing

http://macfusionapp.org/ – mount remote drives (SFTP, etc)locally

http://www.araelium.com/querious/ – MySQL management (SequelPro is better)

http://www.sitesucker.us/home.html – Download website HTML (useful for backing up marketing sites)

 

“Agile” may not mean what you think it means

I was first introduced to “Agile” processes back in 2000, during the first dot com. I was working on a web project, we were trying to get it to market quickly, before the bottom completely fell out, and the engineering contractor suggested trying it. It was a relatively new concept, and a good one. It made sense, and I figured that it would a naturally become the dominant way to run projects.

So I’m constantly surprised that fifteen years later, people are still throwing around the term “agile” like it’s a new thing, and not really getting what it actually means.

So here you go:

According to the dictionary, agile means “able to move quickly and easily.”

In our context – software development – agile means a design and development process that allows a project to adapt to changing markets and business requirements. It’s typically characterized by division of tasks into short phases and frequent reassessment of plans.

In a fast-evolving market (most markets these days), a company can’t identify a need, then take two years to develop a product to meet that need. By the end of the project, the market will have changed and the product will have become obsolete. An agile process may get an initial project to market faster, but it will also allow the company to track the changing market through the duration of the project.

What it doesn’t mean:

  • Faster
  • Cheaper
  • Ad-hoc
  • Disorganized
  • Unplanned

 

People don’t actually  actually use these terms. They use “agile” as a substitute word. A firm says “we’re agile,” and they mean, “we don’t really have a process for that and make it up on the fly” and a client thinks, “great, this project will be fast and cheap.”

This is not agile! This is ad-hoc and crappy.

The problem with “I’m sorry”

“I’m sorry.” Seem simple, doesn’t it? But it’s not – depending on its context, it can mean radically different things, and if we aren’t clear with ourselves and others about it, it can severely impact how we relate with others.

The main problem with “I’m sorry” is that it can mean either sympathy or apology. The distinction between the two seems straightforward, but in common usage the difference is often subtle, even to the person saying it.

“I’m sorry” to express sympathy.

One common use of “I’m sorry” is to express sympathy:

I’m sorry that happened. I’m sorry your goldfish died. I’m sorry you feel sick.

We often feel sympathy for others, and sometimes the best thing to do is to just say it. Saying I’m sorry isn’t apologizing, but it’s expressing sympathy (notably not pity) for someone. This is the easy I’m sorry; the next one is the hard one.

“I’m sorry” to apologize.

The other common use of I’m sorry is to express apology:

I’m sorry I did that. I’m sorry I said that. I’m sorry I made you feel that way.

Apologizing is a key part of healthy communication. A quick Google search will lead to plenty of explanations of how to effectively apologize, but at its core, a sincere apology consists of two key pieces:

  1. An acknowledgement of remorse, regret, or shame over your actions.
  2. An acknowledgement of the hurt your actions have caused someone else.

The problem with “I’m sorry.”

The problem is that it’s easy to substitute an apologetic “I’m sorry” with a sympathetic “I’m sorry.” This looks like:

I’m sorry you feel bad about the thing I did.

This is problematic because it’s often used as an apology without actually apologizing, making it insincere. It addresses the second part of a genuine apology (acknowledging the hurt), but avoids the first part: acknowledging remorse, regret, or shame for the offending actions.

By acknowledging the effects of their actions (the hurt) but acknowledging no regret or remorse for those actions (“I regret that you were hurt, but I don’t regret the actions that led to that hurt”), the transgressor (the one apologizing) abdicates agency in their own actions (“I was forced to do it”).

If they aren’t at fault for the hurtful actions, who is to blame for the hurt? The only agent left is the transgressed. They are to blame – both for causing the hurtful actions to begin with, and for feeling hurt by them:

This hurts me more than it hurts you.

This is sometimes intentional, or even part of a larger pattern of abuse, but it’s often completely unintentional or even self-justified as compassionate:

I genuinely feel bad that those actions hurt her.

Regardless, the effect is the same: this “apology” is not an apology at all. It avoids responsibility, diminishes the transgressed, and shifts blame away from the transgressor. The transgressed is made responsible for the actions as well as the hurt, and the transgressor escapes cleanly.

Our responsibility is to apologize thoughtfully.

It’s our responsibility as compassionate people – in relationships with our partners, our friends, and our colleagues – to understand the subtle and unintended effects of our words. Perhaps we should “I’m sorry” liberally, but conscientiously, and understand how we’re using it when we use it.

Or perhaps we should limit “I’m sorry” to expressing condolences, and not use it to apologize. Instead, we could use this construction: “I’d like to apologize; I regret doing that thing, and know it made you feel bad.”

Thoughts on things, uncollected and poorly written