Jeff Miller's Big Idea Creativity seeking form

So, if you haven’t been closely following the Boyink Family life for the past year and a half or so let me catch you up.  In December of 2009 we made the decision to take a year-long RV-based family road trip.  As part of that I sold my hobby vehicle, a 1964 CJ6 Jeep that I had invested countless hours in.  That Jeep was the latest in Jeep ownership that stretched from the time I turned 18 and included a 1966 CJ5 and a 1952 Willys Wagon. 

Fun in the garage wasn’t limited to just vehicles.  I’ve also made tandem bikes, a quadcycle, and a small junkyard sculpture.

Since coming back from our trip I’ve found myself restless and antsy - especially when the evening hours roll around and I’m done with the days work, am tired of looking at screens and don’t want to read a book.  I think I was driving the family nuts with my frustrated pacing and desire for something to go do.

I was missing an offline hobby.

So last week I hopped in the truck and made a visit to the local metal recycle yard where I grabbed a bunch of scrap metal in various shapes.  I had no preconceived notion of what I wanted to build - but rather just figured something would present itself from the bits I had gathered.

It didn’t take long to see a cat’s head in one of the shapes and car rim suggested the arched back of a angered cat.  With that idea the build was on. Some automotive “A-arms” provided easy legs, a box of nails supplied whiskers, eyebrows, claws, and a spiked tail.  1/2 of a garden rake became the mouth with fangs coming from the ends of some railroad spikes.  I found myself with help at times, with my son doing some of the welding (and even turning down friends at the door to do so).  My daughter dubbed it “Dumpster” and I added the junkyard zombie cat as that’s what came to mind as it came together,.

Enjoy!

If you’re curious about how my family and I spent a year traveling the US by RV while keeping our businesses going, join me in Grand Rapids on February 22 when I’ll be giving a presentation entitled Getting Away With IT.

I’ll talk about the practicalities involved in prepping for the trip, the realities of working from the road, the difficulties of coming back off the road, and how we’re planning to ditch our house and become full time technomads. 

The talk will be geared towards other IT workers, and our hope is to inspire you to realize you have the skillset to consider your own location-independent adventure.

Almost three years ago I ran across the Startup Weekend organization and immediately wanted to do one in West Michigan. I enlisted the help of Aaron Schaap and ElevatorUp and together with some additional volunteers and sponsors the result was Startup Weekend 2010.  As I wrote in my wrap-up post the event was an amazing success that - even if all the businesses don’t ultimately make it - makes a positive impact on the business scene to offset all of the negative press.

The saddest part of the experience for me was that, due to our plans for an extended family RV roadtrip for 2011 we wouldn’t be around for the event.

But, here we are for 2012 - back from our trip and in West Michigan for the winter.  While we’d still rather be somewhere warmer one of the upsides was being here for StartupWeekend 2012. Showing up at The Factory Friday night I could immediately sense the event was starting to hit its stride.  Pre-printed name tags, business-plan related books and materials, and t-shirts were all ready for us.

The event’s growth was apparent both in the number of attendees but also the number of business-idea pitches.  We had 18 the first year and 32 this year.  The voting process netted 11 ideas and teams formed around them. 

I joined the team working on an idea for a website & app that addresses a life situation that seems uncomfortable to talk about - what happens to your stuff when you die.  While wills and trusts can be created to cover the big things, they don’t always cover the small items that aren’t valuable in dollars but still have emotional value.  The team pitching the idea already had a name for it - ThisGoesTo.  Our work for the weekend included some online and in-person surveys to validate the idea, refining the core description of the service, putting together a mockup of the app, and adding a beta signup to website.  We also modelled a revenue model, estimated startup costs, and defined the core audience for the business.

Startup Weekends culminate in a presentation of your work and the presentations are all reviewed by a panel of judges.  The audience for the presentations is mainly the other teams but also includes bankers, lawyers and venture capitalists. 

Oh and?  You get 5 minutes. 5 Minutes to communicate your idea, how you validated it, what it does, who will buy it, how much they’ll pay and demo anything you have working.  The 5 minutes is strictly enforced - if you are still talking you get cut off. 

I felt we were lucky to have a spot in the middle of the pack - it gave us some time to view presentations from other teams and make adjustments to ours.  We had a skit planned to start with and trimmed that down to make sure we had enough time to get through everything.  I ended up being the presenter and after seeing some other teams get cut off I really wanted to stick the landing.

The result?  We recieved an “honorable mention” from the judges - but don’t take their word for it.  The presentations were recorded and posted online by the good folks at DVS:

Here’s the Startup Weekend presentation for ThisGoesTo:

I’m quite pleased with our effort and result.  Thanks so much to everyone on the ThisGoesTo team, and especially Tyler Mikev who hopped in from another team to put together our iPad mockup - and who I neglected to thank while holding the mic.

Just like the first year, I’m amazed at the talent that shows up for a StartupWeekend and what can be accomplished over the course of 54 hours.  I had a great time and look forward to seeing where these startups go!

It seems like every couple of weeks I get an email along these lines:

We have a website that cannot be completed by the current developers….is this something you would like to work on?

Over the years I’ve responded differently, from simple one-line “no thanks” to more involved responses declining the work.  I thought I’d write up a more detailed blog post both to record my thought process in responding as a link to send out in the future.

Who Fired Whom?
As the potential late-comer to the project, unfinished projects are little mysteries waiting to be solved, and you’re asking me to put on my trenchcoat. 

You are only telling me one side of the story and using vague words that make me suspicious.  Are the current developers unable to complete the site because they don’t have the technical savvy? Or the developer doing most of the work took a new job?  Did their salesperson over-promise? 

Then there is the other side of the coin - what if the current developers have stopped working on the project because you stopped paying them?  Or you were a horrible client with shifting expectations and schedules?  Did you not, as a potential client looking to spend thousands of dollars, do your due diligence in finding a development partner capable of building what you needed?  To be a bit crass, why are you coming to me now in “salvage a failure” mode but not when the project was new?

All of this is probably answerable with a few uncomfortable phone calls to both parties, but maybe not. Will you be totally upfront about these issues or gloss over them in hopes of getting me signed on? Either way, will you compensate me for the time spent researching the project history?

Increased Costs
Speaking of getting paid - does the project have any budget left? Or has the current developer soaked up all the profit leaving the nit-picky (and time consuming) details undone that are tough for me to quote or you to pay for by the hour? 

Don’t forget the reverse-engineering time. A web project is not a web project. Different developers have different methodologies and any half-baked site that’s getting turned over to a new developer is going to need to be reverse-engineered by the new guy. If your current developers did a great job documenting what they did this might be easy, but if they aren’t able to complete the work what are the odds of them doing a good job with documentation? More likely I would have to go through everything line by line to get a sense of the build approach. That time also needs to be compensated, so are you prepared for spending more than you initially budgeted to get this project done even though the scope hasn’t changed?

Possible Junk
What if the existing work sucks? I’ve logged into some sites that were horribly built and not even close to something I’d feel comfortable delivering to a client or having my name associated with. Are you prepared to pay me several hours time to both investigate the failure situation and reverse-engineer the site only to come back and tell you it’s a lost cause?

High Risk, Little Reward
Projects in failure mode are risky. People involved in trying to salvage them are tense - someone expected this thing to be done by now and it’s not. Trust has already been broken so the second guy is going to have to work harder to earn it. The project now has baggage - the initial developer will continue to be the elephant in the room during the rest of the project development. Budgets are usually thin and it’s hard to justify spending even more money on something that’s already a failure. The second guy isn’t responsible for the project being in failure mode but is expected to take on the stress of getting it done - a virtual super-hero flying in to scoop up the fallen heroine and fly her to safety just before the earth cracks wide open.

Ultimately the risk is only worth it if either the reward is greater than taking on a project in non-failure mode or the potential second developer doesn’t have any other less risky and stressful projects to do. I’ve never needed the work that badly and haven’t been able to bring myself to charge significantly higher rates to a client in this position. But that doesn’t give (possibly innocent) clients in this position a way out of this mess.

Any Advice
How about you other developers?  Have you taken on a project in failure mode? How did it go? Are there ways to surmount the challenges as the newcomer to the project? Or did it end as it began? Would you do it again?

It seems like every couple of weeks I get an email along these lines:

We have a website that cannot be completed by the current developers….is this something you would like to work on?

Over the years I’ve responded differently, from simple one-line “no thanks” to more involved responses declining the work.  I thought I’d write up a more detailed blog post both to record my thought process in responding and as way to have a link to send out in the future when these requests come in.

Who Fired Whom?
As the potential late-comer to the project, unfinished projects are little mysteries waiting to be solved, and you’re asking me to put on my trenchcoat. 

You are only telling me one side of the story and using vague words that make me suspicious.  Are the current developers unable to complete the site because they don’t have the technical savvy? Or the developer doing most of the work took a new job?  Did their salesperson over-promise? 

Then there is the other side of the coin - what if the current developers have stopped working on the project because you stopped paying them?  Or you were a horrible client with shifting expectations and schedules?  Did you not, as a potential client looking to spend thousands of dollars, do your due diligence in finding a development partner capable of building what you needed?  To be a bit crass, why are you coming to me now in “salvage a failure” mode but not when the project was new?

All of this is probably answerable with a few uncomfortable phone calls to both parties, but maybe not. Will you be totally upfront about these issues or gloss over them in hopes of getting me signed on? Either way, will you compensate me for the time spent researching the project history?

Increased Costs
Speaking of getting paid - does the project have any budget left? Or has the current developer soaked up all the profit leaving the nit-picky (and time consuming) details undone that are tough for me to quote or you to pay for by the hour? 

Don’t forget the reverse-engineering time. A web project is not a web project. Different developers have different methodologies and any half-baked site that’s getting turned over to a new developer is going to need to be reverse-engineered by the new guy. If your current developers did a great job documenting what they did this might be easy, but if they aren’t able to complete the work what are the odds of them doing a good job with documentation? More likely I would have to go through everything line by line to get a sense of the build approach. That time also needs to be compensated, so are you prepared for spending more than you initially budgeted to get this project done even though the scope hasn’t changed?

Possible Junk
What if the existing work sucks? I’ve logged into some sites that were horribly built and not even close to something I’d feel comfortable delivering to a client or having my name associated with. Are you prepared to pay me several hours time to both investigate the failure situation and reverse-engineer the site only to come back and tell you it’s a lost cause?

High Risk, Little Reward
Projects in failure mode are risky. People involved in trying to salvage them are tense - someone expected this thing to be done by now and it’s not. Trust has already been broken so the second guy is going to have to work harder to earn it. The project now has baggage - the initial developer will continue to be the elephant in the room during the rest of the project development. Budgets are usually thin and it’s hard to justify spending even more money on something that’s already a failure. The second guy isn’t responsible for the project being in failure mode but is expected to take on the stress of getting it done - a virtual super-hero flying in to scoop up the fallen heroine and fly her to safety just before the earth cracks wide open.

Ultimately the risk is only worth it if either the reward is greater than taking on a project in non-failure mode or the potential second developer doesn’t have any other less risky and stressful projects to do. I’ve never needed the work that badly and haven’t been able to bring myself to charge significantly higher rates to a client in this position. But that doesn’t give (possibly innocent) clients in this position a way out of this mess.

Any Advice?
How about you other developers?  Have you taken on a project in failure mode? How did it go? Are there ways to surmount the challenges as the newcomer to the project? Or did it end as it began? Would you do it again?

Nearly six years ago I made a similar announcement - the launch of TheVillaPassalacqua.com on ExpressionEngine. 

Oops, I did it again.

The big news in 2006 was getting the site out of Flash and onto a CMS so the owner of the Villa could manage the content himself.  After 5+ years, however, the design was showing it’s age and the site wasn’t performing as well in search engines as it used to.  Earlier this year we set out on a redesign effort to address both of those issues.

For the visual design I enlisted the help of Erwin Heiser of Stookstudio. Erwin is an old ExpressionEngine friend and I felt his clean, elegant and international style was a good fit for this project.  For better input on a search strategy I enlisted the help of the East Lansing, MI based NetVantage Marketing.  The folks there helped with getting some baseline analytics in place and doing some keyword research that I used to put the overall architecture & strategy together.  New photography was a key aspect of this effort and the client sourced a local provider in Italy for that work - with great results.  The imagery really carries the site from a visual perspective.

Part of the overall strategy was also launching some one-page sites based on the targeted keywords that the initial research drove out, so along with the main site launching we also put live:

TheVillaBellini.com
WeddingsLakeComo.com
Luxury-Italian-Villas.com
LakeComoVillaRentals.com

All of these domains are run out of one installation of ExpressionEngine using the Multi-Site Manager for separating out content on the back end. This whole multi-site approach is arguably a bit experimental.  We’ll track where traffic goes and make changes to the overall approach based on success or failure in any one area. 

Thanks to everyone involved - nice to get this live before year-end!

I’m pleased to announce the launch of a new client site: MorganFranklin.com.

The site design is by Grand Rapids, Michigan based Visual Hero and the front-end code was done by Andy of Ford Interactive out of the Sacramento, California area.

The project was an interesting one for a number of reasons:

EE1 - EE2 Upgrade
The previous version of the site was built in ExpressionEngine 1 by another agency. This meant that not only did I have the challenge of an upgrade, it had to be done to a site that I didn’t build initially so wasn’t as familiar with.  I won’t lie - the process was tedious and did take a couple of attempts.  I kept notes during the process and plan to write an article on Train-ee outlining my approach.

New IA
The driving purpose for the redesign was that MorganFranklin had changed the way they thought about and described their business.  This necessitated an information architecture change on the site which in turn meant that the content structure in the existing EE backend no longer had a close relationship to the front-end.  Further compounding the challenge here was that site had a decent amount of content and based on the project timeline the goal was to do as little content re-working as possible.

The solution?  An add-on!  (I’ll pause here while the collective EE community recovers from shock).  In this case the Taxonomy Module from developer Iain Urquhart successfully bridged the gap between backend content structure and front-end navigation structure while giving the client a new sense of control over their navigation.

New Template Code
While the content stayed relatively stable I re-worked the entire site from a template code perspective in an effort to be more DRY.  I still want to do a more detailed benchmarking report (and some things may still change for performance reasons) but the number of templates went from 113 to 41 and the number of channels from 17 to 11.

Built on the Fly (but not like that)
As you may or may not know, I spent the last year travelling the US by RV and I worked on this site during that trip.  Near as I can tell this is a “21-state website” getting worked on from Georgia to the west coast, then up to Washington and back across the plains to Michigan. 

Thanks to Visual Hero and Ford Interactive for their part in the project, and thanks to MorganFranklin for being flexible and working with a mobile developer!

Up for sale is our one and only “real” piece of furniture left - a classic and authentic Eames Lounge Chair and Ottoman.  While we’ve enjoyed owning this chair it doesn’t fit our now-mobile lifestyle so we’re looking for a new home for it.

The chair is approximately 13 years old and shows normal wear on the black leather.  The wood is all in nice shape yet.  A couple of years ago the mount where the chair back attaches to the armrest did come apart - the glue had dried up. I disassembled the chair and sent the necessary pieces back to Herman Miller for a factory repair.

The ottoman was purchased later and is approximately 5 years old.  It does have on approximately 3” long scratch in the leather as shown in picture.

The chair is located in Holland, MI and at this point is for sale by pickup only, cash, money order or bankers check only.  The chair is in storage so contact us to arrange viewing.

This set sells new for around $4500, our price is $3000.00 firm, no trades.

I am about to blog about clothes. 

This is something new for me.  I don’t think over the ten-odd years I have been blogging I have ever blogged about clothes.  But over the last couple of months clothes have been a large topic of thinking and conversation between MsBoyink and I.  We’ve been focusing so much on clothes because we’re tired of thinking about what to wear.

We’ve discovered that there are two main ways to think about your wardrobe at a high level and what to wear on a daily level:

• Don’t think about your wardrobe - let it grow organically.  Decide what to wear on a daily basis based on what’s available and goes together
• Look at your wardrobe as a system, developing a common base and color scheme.  Spend almost no time on a daily basis because the core pieces are the same and it all goes together

I have always taken the (lazy) #1 approach to my wardrobe.  It consisted of items bought or received piece by piece.  I had a drawer full of t-shirts in a wide array of colors, blue jeans, and the odd pair of khakis.  Up top I had a collection of button-up shirts that I liked on an individual basis, but that could only be worn with certain t-shirts. Many days this was fine - especially if I had no meetings or public outings planned.  But weeks where I would be teaching or at a conference it meant I had to plan what I could wear daily in advance by finding and creating pairings.  Wearing the wrong t-shirt early in the week meant I’d be shorthanded later or have to wear the same t-shirt twice.

Then I ran across this article by a person I had sat four feet away from on a daily basis for over a year. Go read that.  I never noticed her basic wardrobe didn’t change. Her reasoning not only makes sense to me but the idea of not having to think so much about clothes on a daily basis sounded freeing.

So I’ve set out to create my own personal uniform.  I’m almost there and am quite pleased with the results so far.  Here’s my journey:

The Gray T-Shirt
Let me back up a moment.  I need to make the context of this wardrobe approach clear.  If you aren’t familiar with my story, over a year ago I set out on an year long family RV road trip adventure.  We’re currently back in our home town, but have decided that one year wasn’t enough so after a few months of decision making and work projects we’ll be setting out again indefinitely.  What this means from a clothing perspective is that I need a wardrobe that can accommodate a wide variety of temperatures and social settings.

I needed to start with a t-shirt, one color that would work for everything.  In the past I would have considered white but what we found on our travels is that it’s impossible to keep white white.  That’s due to both being more active and outdoors, but also due to doing laundry in places with less than ideal water.  Our whites all look pretty bad at this point.

My second choice was black, but when we’re out hiking on sunny warm days in places like Arizona black doesn’t work so well. Navy would have the same problem.

So it was down to gray - light enough to be comfortable in the sun but dark enough to hide dirt & water stains.  I looked around online thinking I would buy a week’s worth of t-shirts from a high-quality supplier like Lands End or Woolrich, only to find that reviews of their latest products were poor (and many of those reviews from people who’d been buying the same t-shirts for years).  I liked the look of these American Apparel “Military Surplus Tees” but I ended up in a pinch. I was packing for a conference, the laundry wasn’t caught up, and all my t-shirt options were bright colors and didn’t work for the shirts I wanted to wear. I went out and found that the local Target had just placed a fresh display of Jerzee t-shirts and they had seven gray ones in my size for $5/ea. Sold.

Dickies Carpenter Pants
With the basic t-shirts selected it was easier to choose pants.  I’ve been a life-long wearer of Levis but haven’t been as happy with the quality of my last couple of pair.  It seems like they are about 1/2 the thickness they used to be and just don’t hold up as well.  I also wanted something just a bit dressier than basic jeans while staying as comfortable.

I came across the Dickies line being sold at Wal-Mart and found the Relaxed Fit Carpenter Jean in the olive color that would work well with the gray t-shirt.  I bought one pair as an experiment and after a couple of weeks and a couple of washings liked how they felt & fit, so bought another pair.  Actually this proved out an advantage of a standardized wardrobe - I couldn’t find another pair in my size in the olive color locally so just ordered them online.

Sketcher Shoes
Shoes have been a puzzle.  For the last few months I’ve had exactly one pair of shoes - some Keen sandals.  I love them but even with dark socks I don’t feel quite comfortable wearing them to client meetings.  I had thought to buy some shiny black shoes to dress the look up a bit, but then I tried on pair of Skecher Browsers and found them to be the perfect middle-ground shoe, casual enough to wear with just a t-shirt and dressy enough to wear with a button up shirt or more.

Topping It Off
So gray t-shirts, olive carpenter pants, and a pair of Skechers form the basis of my new “uniform”.  But maybe it’s not actually a uniform, because from there I can wear any number of short or long sleeve button up shirts that are either solid or plaids with navy, white, black or grey colors. I also have a couple of navy Henley-style pullovers that will work in this system. 

Beyond the Basics
I plan to buy two more pair of pants in the same olive color.  One a more traditional dress pant for times when I have to meet with corporate clients on their turf.  The second a pair of out-door hiking style pants with zip-off legs which will also add a pair of shorts to the mix.  I might still have a sport-coat that will go with this color scheme - if it didn’t get purged in our pre-trip preparations.  If it’s gone I probably won’t rush to replace it but know I could throw one in the mix if need be.

Coats needed to be considered - I’ve a lightweight black nylon fall coat that will work for mild temps, and a Lands’ End Squall Jacket in navy for colder temps. Nothing new needed there.

The Results
I love it.

On a daily basis I can grab the basics while I’m still half asleep.  Up top I can grab anything that makes sense based on the weather for the day.  Packing for trips is way easier - I just count the number of days I’ll be gone and toss in enough t-shirts and shirts without worrying about pairings or sequences.  Laundry is easier because it all can go in the same load.  Purging my existing wardrobe was easy - items either worked with the new scheme or they didn’t.  Christmas gift recommendations can be very specific down to item and color.

This particular quote from the article I linked to above has stuck with me:

But the truth is, most people pay more attention to what they are wearing — and whether it’s appropriate, fitting, tucked correctly, accessorized appropriately, or not — and not to what you are wearing. My clothes are not nearly as interesting as the reason my clients want to meet with me — which is them and their business, driving their success. And that’s as it should be.

If I can’t remember what other people wore the day before, why should I worry what they think about my clothes?

I’m not a fashionista.  I don’t need to make statements with my clothes.  I just want to look “put together” and professional enough that I feel comfortable and don’t look out of place in different social settings.  And now I can do that almost without thinking about it.

I am about to blog about clothes. 

This is something new for me.  I don’t think over the ten-odd years I have been blogging I have ever blogged about clothes.  But over the last couple of months clothes have been a large topic of thinking and conversation between MsBoyink and I.  We’ve been focusing so much on clothes because we’re tired of thinking about what to wear.

We’ve discovered that there are two main ways to think about your wardrobe at a high level and what to wear on a daily level:

• Don’t think about your wardrobe - let it grow organically.  Decide what to wear on a daily basis based on what’s available and goes together
• Look at your wardrobe as a system, developing a common base and color scheme.  Spend almost no time on a daily basis because the core pieces are the same and it all goes together

I have always taken the (lazy) #1 approach to my wardrobe.  It consisted of items bought or received piece by piece.  I had a drawer full of t-shirts in a wide array of colors, blue jeans, and the odd pair of khakis.  Up top I had a collection of button-up shirts that I liked on an individual basis, but that could only be worn with certain t-shirts. Many days this was fine - especially if I had no meetings or public outings planned.  But weeks where I would be teaching or at a conference it meant I had to plan what I could wear daily in advance by finding and creating pairings.  Wearing the wrong t-shirt early in the week meant I’d be shorthanded later or have to wear the same t-shirt twice.

Then I ran across this article by a person I had sat four feet away from on a daily basis for over a year. Go read that.  I never noticed her basic wardrobe didn’t change. Her reasoning not only makes sense to me but the idea of not having to think so much about clothes on a daily basis sounded freeing.

So I’ve set out to create my own personal uniform.  I’m almost there and am quite pleased with the results so far.  Here’s my journey:

The Gray T-Shirt
Let me back up a moment.  I need to make the context of this wardrobe approach clear.  If you aren’t familiar with my story, over a year ago I set out on an year long family RV road trip adventure.  We’re currently back in our home town, but have decided that one year wasn’t enough so after a few months of decision making and work projects we’ll be setting out again indefinitely.  What this means from a clothing perspective is that I need a wardrobe that can accommodate a wide variety of temperatures and social settings.

I needed to start with a t-shirt, one color that would work for everything.  In the past I would have considered white but what we found on our travels is that it’s impossible to keep white white.  That’s due to both being more active and outdoors, but also due to doing laundry in places with less than ideal water.  Our whites all look pretty bad at this point.

My second choice was black, but when we’re out hiking on sunny warm days in places like Arizona black doesn’t work so well. Navy would have the same problem.

So it was down to gray - light enough to be comfortable in the sun but dark enough to hide dirt & water stains.  I looked around online thinking I would buy a week’s worth of t-shirts from a high-quality supplier like Lands End or Woolrich, only to find that reviews of their latest products were poor (and many of those reviews from people who’d been buying the same t-shirts for years).  I liked the look of these American Apparel “Military Surplus Tees” but I ended up in a pinch. I was packing for a conference, the laundry wasn’t caught up, and all my t-shirt options were bright colors and didn’t work for the shirts I wanted to wear. I went out and found that the local Target had just placed a fresh display of Jerzee t-shirts and they had seven gray ones in my size for $5/ea. Sold.

Dickies Carpenter Pants
With the basic t-shirts selected it was easier to choose pants.  I’ve been a life-long wearer of Levis but haven’t been as happy with the quality of my last couple of pair.  It seems like they are about 1/2 the thickness they used to be and just don’t hold up as well.  I also wanted something just a bit dressier than basic jeans while staying as comfortable.

I came across the Dickies line being sold at Wal-Mart and found the Relaxed Fit Carpenter Jean in the olive color that would work well with the gray t-shirt.  I bought one pair as an experiment and after a couple of weeks and a couple of washings liked how they felt & fit, so bought another pair.  Actually this proved out an advantage of a standardized wardrobe - I couldn’t find another pair in my size in the olive color locally so just ordered them online.

Sketcher Shoes
Shoes have been a puzzle.  For the last few months I’ve had exactly one pair of shoes - some Keen sandals.  I love them but even with dark socks I don’t feel quite comfortable wearing them to client meetings.  I had thought to buy some shiny black shoes to dress the look up a bit, but then I tried on pair of Skecher Browsers and found them to be the perfect middle-ground shoe, casual enough to wear with just a t-shirt and dressy enough to wear with a button up shirt or more.

Topping It Off
So gray t-shirts, olive carpenter pants, and a pair of Skechers form the basis of my new “uniform”.  But maybe it’s not actually a uniform, because from there I can wear any number of short or long sleeve button up shirts that are either solid or plaids with navy, white, black or grey colors. I also have a couple of navy Henley-style pullovers that will work in this system. 

Beyond the Basics
I plan to buy two more pair of pants in the same olive color.  One a more traditional dress pant for times when I have to meet with corporate clients on their turf.  The second a pair of out-door hiking style pants with zip-off legs which will also add a pair of shorts to the mix.  I might still have a sport-coat that will go with this color scheme - if it didn’t get purged in our pre-trip preparations.  If it’s gone I probably won’t rush to replace it but know I could throw one in the mix if need be.

Coats needed to be considered - I’ve a lightweight black nylon fall coat that will work for mild temps, and a Lands’ End Squall Jacket in navy for colder temps. Nothing new needed there.

The Results
Here’s a couple of pictures from a recent conference where I was “in uniform”:

I love it.

On a daily basis I can grab the basics while I’m still half asleep.  Up top I can grab anything that makes sense based on the weather for the day.  Packing for trips is way easier - I just count the number of days I’ll be gone and toss in enough t-shirts and shirts without worrying about pairings or sequences.  Laundry is easier because it all can go in the same load.  Purging my existing wardrobe was easy - items either worked with the new scheme or they didn’t.  Christmas gift recommendations can be very specific down to item and color.

This particular quote from the article I linked to above has stuck with me:

But the truth is, most people pay more attention to what they are wearing — and whether it’s appropriate, fitting, tucked correctly, accessorized appropriately, or not — and not to what you are wearing. My clothes are not nearly as interesting as the reason my clients want to meet with me — which is them and their business, driving their success. And that’s as it should be.

If I can’t remember what other people wore the day before, why should I worry what they think about my clothes?

I’m not a fashionista.  I don’t need to make statements with my clothes.  I just want to look “put together” and professional enough that I feel comfortable and don’t look out of place in different social settings.  And now I can do that almost without thinking about it.