Advice

A Writer’s Life: Cover Me II: Electric Boogaloo

by

(This column is posted at www.StevenSavage.com and Steve’s Tumblr)

Sorry for all the delays in actually posting on writing.  been a weird few weeks.  So I want to talk about Book Covers again – with an interesting exercise.

I was thinking about my future writing plans.

First, the covers for the new Way With Worlds books were OK, but I realized I didn’t have the skills/intuition to have made them jazzier.  In fact, I wasn’t sure they needed to be jazzier, and realized I lacked artistic insights.

Secondly, I’ve considered revising and updating some past books, and that would mean covers.  For some I didn’t want to go purchase new art, especially for more niche works.

Third, my “Big Books” usually have paid art.  But what of smaller books, or less “eventful” books?  Sure I could buy a cover, but I had some skills, so why couldn’t I make better covers?

Thus, I set myself a project – to build 30 covers in gimp (because I am cheap) before the end of the year if not earlier.  This way I’d at least have the skills to make a decent book cover, and more than enough skills for books that might not need something jazzier.

I did this by:

  1. Using the free photos at pixabay.com when I need them.
  2. Looking at various book covers and seeing what I could learn from them about what made them “work” – from classic sci-fi to cheese romance.
  3. Finding new gimp techniques and trying them out.
  4. Trying to duplicate different genres and feels.

You can see the results at my tumblr, and I think I’ve definitely gotten better.  In fact, the improvement rate has been pretty remarkable.

This is a great technique to improve anything – build a project with no “critical deliverable” but a goal and try it out.  It could be used for more than just covers – it could be for writing, cooking, and so on.  Take what you want to learn and make a fun project out of it.

However for you indie artists, this may be worth trying yourself.  All you need is the gimp and some photos.  If you build enough skills, then you’re just some time and maybe a royalty-free (or self-taken) photo away from a book cover.

 

– Steve

MVP and Anxiety (My Agile Life)

by

(This column is posted at www.StevenSavage.com, Steve’s LinkedIn, and Steve’s Tumblr)

This is an odd post. In some ways it’s about psychology. In some ways it’s about my use of “Agile” and Scrum  in my life. Either way, I think you’ll find it valuable, even if you’re not reading those posts.

Imagine that you have a problem to solve, but you’re not sure how to solve it. Worse, this situation is complicated by having many options – a common problem in a wired age with so much at our fingertips. You’re paralyzed by choice and fear of the wrong choice – so what do you do and how do you get out of this?

There is a solution – and one that comes from Agile and Lean techniques. Yeah, I know, trust me on this and keep reading.

The solution is something called Minimum Viable Product or MVP. In software and general terms, it means something that delivers the minimum needed to go to market and satisfy customers and get feedback. To get an MVP you carefully look over what you have to do, pick the effective minimum for the audience, and get it done right.

In fact, an MVP may be all you need for a while. Consider how many people or companies use bare-bones web pages with nice graphics and don’t need any more. You can apply this philosophy to your life.

To use MVP in your life, from plumbing to writing, ask yourself what is the minimum you need to do well to get something complete and ready. Sit down, list your concerns or needs or whatever, pick only the ones that must be done, and do them. You’ve solved your problem, and if it’s not perfect, you can tweak it later if you need to.

(And yes, that’s over-simplified, but it’s enough to get you started.  MVPs for products get more complex.)

Here’s a few examples:

  • You want to have premade lunches for a week so you make a big pot of chili and garnish it differently each day. Next week you might cook two different meals at once, but this is done for the week so you can relax.
  • You want to get a chapter of a book to an editor, so you make sure it’s clearly readable without fiddling with it endlessly. The editor can take it the rest of the way so you’re not caught in a writer’s panic.
  • Traffic is crazy due to construction, so you find a path to work that, if not the fastest, is the least likely to be congested. For the rest of the month your commute is longer than usual, but it’s predictable.

These solutions are not perfect but they are good enough and they get you on your way. In some cases they’ll save you time from worrying more than doing.

The other benefit of MVP is that going for the MVP prevents what’s called paralysis through analysis in the business world – overthinking. MVP gets you on your way and moving forward. In turn, the fact you are at least done means you can reflect on what you did, what you need, and improve things later. Sometimes you don’t even know what you need until you’ve done something after all.

In many cases – especially in life – the MVP is all you need for a long time, maybe forever. Sure you repainted the bedroom the exact same color, you didn’t spend hours debating colors like “Thupe” and “Preamble Brown”. Yes, the report at work could look a bit better but no one cares about the cover color. MVP can often bring you back to reality as well as keep you from anxiety.

Next time you have to fix something or do something, think about the MVP. It’ll focus you on value, keep you from over-elaborating, and reduce anxiety.

(By the way I do plenty of books for coaching people to improve in various areas, which may also help you out!)

– Steve

My Agile Life: Overwork

by

(This column is posted at www.StevenSavage.com, Steve’s LinkedIn, and Steve’s Tumblr)

(My continuing “Agile Life” column, where I use Scrum for a more balanced and productive life continues).

Uhg.  So as you know from my blogging about agile techniques, I’ve been getting overloaded.  I’m trying to fix this with some success.  So here’s what I’ve been trying.

  • Velocity.  Velocity, the measure of work done in a timeframe, is a big part of Scrum.  One reason to measure it is to see what you can do – but another is to make sure you’re not overloaded.  I can tell my usual workload doesn’t quite work out, so I’m trying to reduce it a bit here and there.  EXAMPLE: Restructuring how much I put into a given project a month.
  • Effectiveness.  Do things better.  I’ve found you can also save time just by doing stuff better.  EXAMPLE: I made graphic templates for upcoming graphic work.
  • Letting go of the schedule.  Work done on time doesn’t matter if it’s poorly done.  You have to re-evaluate and re-assess your schedules and in some cases dispose of them entirely.  EXAMPLE: I had some library donations to make that kept getting interrupted, so I had to accept “it gets done when it gets done.”
  • Iterativeness.  The flipside of efficiency is to not try to be perfect.  Some things are iterative, things you do over and over or regularly.  These can be improved, or mistakes compensated for.  EXAMPLE: Cleaning.  If I miss a hard water stain in the shower it won’t kill me as I’ll fix that next week.
  • Capture.  Be sure to capture any big blocks of time you want to use for something.  EXAMPLE: I have some convention speaking coming up so I literally put it in my schedule as a big block of time to note “I will be doing nothing else then.”
  • Sizing.  I’m sticking with the Fibonacci numbers for sizing my work – in hours – as it seems to produce better estimates.

I’ve also looked at things that mess up my planning and scheduling and productivity.  The Antipatterns.  They are

  • Loading Up.  When you find your maximum velocity of work, it doesn’t mean it’s what you should do.  It’s what you’re capable of when you push yourself.  What is you sustainable rate?
  • Lumping.  When possible break things down so you can calculate your workload – and because it lets you adapt better.
  • Missing lumps.  Some things are just purely about a time commitment, like “setting aside X hours to relax.”  Some things are better lumped together just so you’re not micromanaging.
  • Not looking at value.  When you do something ask what makes it useful – believe me there’s some surprises in there.
  • Bad Deadlines.  Again, deadlines should serve quality, not the other way around.
  • No goals.  When you don’t have goals, you can’t plan.  We often substitute panic, deadlines, etc. for goals – those aren’t goals.  Goals are positive.
  • Done over quality.  Doing something fast poorly can be worthless.
  • Rigidity.  Agile methods are about embracing change, and if you have to keep things rigid, you’re not Agile.  You need to find ways to be adaptable.

Hope these help you out.  Something to look out for in your own life – and anyone you manage.

(By the way I do plenty of books for coaching people to improve in various areas, which may also help you out!)

– Steve