Behind the Scenes at Global-Roam

Post updated on 1st February 2010 to clarify the primary KPI.

This post is designed to provide an overview of what is required.  Note that (if you are successful in your application) I would expect that you would be proactive in working with me to flesh out the details of this position, in terms of specific deliverables and dates!

I have spoken with a number of people (online and offline) over the course of the past few months, since I determined that we needed to hire you.

It seems that no job title that could encapsulate this role is universally understood.  For this reason, you will be known as our:

General Manager for Discerning, Developing and Delivering what the Customer Wants

Bit of a mouthful, I know, but all three aspects of the role are important.

read more »

UI Fundamentals for Programmers by Ryan Singer from ChicagoRuby on Vimeo.

The post below is an early draft (and is incomplete).

It has been superseded by a more recent update, which I posted here on the blog on Thursday 25th February 2010.  The post below remains here (for now) as a historical curiosity.

---

The role of the Product Manager follows a similar model as that we will apply to our Chief Software Engineer and, as such, the position might be equally termed:

Manager for Discerning, Developing and Delivering what the Customer Wants

Again, all three aspects of the role are important.

1)     Summary

As Product Manager, you will accept direct responsibility for one (or more) of our Mature Products.

With this responsibility, your focus will be on maximising the value we deliver to clients through this product – whilst at the same time maximising the value we generate for ourselves, over the longer-term.

You will also accept responsibility as a Project Manager in the software development process – utilising the Agile methods promoted by the Chief Software Engineer.

If necessary, you will also play a role in coding, though this will not be your primary focus.

---

read more »

I posted, early in January, about where our bus is headed (you might refer to this as our Vision).  I have progressively refined this, since then, to improve the clarity of this core message.

For those who are interested, I have also started posting more details about some aspects of this Vision – as falling under any of these core headings.  This post provides more details under the first heading.

As part of the navel-gazing we have been doing recently (to coincide with our 10th birthday, which is rapidly approaching) we have been contemplating this question.  For us, there are plenty of opportunities (some mutually exclusive – at least for a company our size).

Being New Year’s Day, I thought it would be of interest to you to post a few comments about where our bus is headed into the future. Call this our very own New Year’s resolution.

read more »

.

Here’s an interesting video (runs for an hour) promoting a new book “Glimmer:  How Design Can Transform Your Life, and Maybe Even the World” by Warren Berger (and Bruce Mau).

Seems like an interesting book, so have thrown it in our shopping cart, and will review it sometime in 2010.

read more »

.

Had to chuckle one night last week when I saw (in one of the many books I am reading at present) the following passage:

When I was studying [about software] at [uni], it was common to talk to professors and students about new products.  We’d focus on what components these new software products used and how they compared against what could have been.  Value was … how much of the latest technologies they used.

Generally, we thought everything sucked.  Very few products survived our critiques.  We wondered why the marketplace was packed with mediocrity and disappointment.

We’d even invented geek conspiracy theories to explain the evil decisions, which we thought were made against engineering purity and thus made little or no sense to us.

Often, we’d focus blame on the marketing departments of these companies (not that many of us understood what marketers did).

Even in my first few years in the industry, the same kinds of conversations took place again and again.

Actually, it was more of a liberal dose of belly-laughter than just a chuckle, which brought a look of consternation from my wife.

read more »

Here’s another back-dated post, with a date chosen shortly after Joel’s post to which it refers.  I’ve done this to ensure that these comments are read in context.

My apologies to those for whom this practice offends – as noted before, I believe ICT is an enabler, not an ends in itself (or, to put it another way, I am not interested in form without substance).

.

1)     Introduction to Joel’s Post

Back on November 1st, Joel Spolsky made a post for Inc magazine entitled “Does Slow Growth Equal Slow Death?”.

One of the guys in the office found this, and it stimulated a bit of discussion internally about where our bus is headed (on a restricted post).  This was good, as we had commenced our Autopsy 2 process. read more »

.

One of our central focuses back in our Business Autopsy in July (which we’re now starting to think of as Autopsy 1 - as distinct from the current Autopsy 2), was the fact that our software development processes were not up-to-scratch. read more »