This was a fun project filled with complex design problems. Fundamentally designing a product to support both Fortune 500 companies with 30k users and small companies with 20 users is always a challenge. Ultimately, I think the new solutions and approaches will improve the user experience and highlight best practices and capabilities currently obfuscated by the interface.

OPUS will continue supporting many of the existing features that has made HumanConcepts’ solutions successful, while simplifying key aspects such as:

• Chart definition and creation (how the charts are displayed)
• Domain management (where the chart information comes from)
• End-user experience (how the charts are used)

Once the new product is released, I will describe specific features in more detail. The initial release of OPUS is due out in Q3 of 2010.

Bumpr is the social messaging utility that helps people manage communication and create lasting communities.  Unlike simple microblogs (e.g., Twitter) or aggregators (e.g., Friend Feed), Bumpr manages incoming and outgoing communication across multiple social networks.

Unlike existing social networks, Plumkeeper lets the parents control who is allowed to see or contribute to the information.  This control allows parents to document everything in one place – regardless if the rest of the family and friends should be kept in the loop.

Now, the really cool part is how parents can contribute… however it’s convenient at the time.  Phone, email, IM, SMS etc.  They’re all ways to easily capture the moment, no matter where you’re at or what you’re doing.  This allows parents to capture those cute little moments when a child discovers something, says something or does something.  Once captured, parents can go back to elaborate on the event, add additional content such as pictures, and ultimately create a physical production (e.g., a memory book).  This makes documenting a child’s life for later nostalgia (or diner torture with a date) a cinch.

I had a great time working with this crew and hope to see a spectacular product develop over the next couple years.  Assuming I ever get around to that whole family thing, I know I’d want to use something like this.

Alight is currently a desktop application (v5 was released recently).  The next major revision will move away from the old desktop process to a browser-based client-server architecture.  This is being done for a few reasons.

• Support for an increasing number of participants in the budgeting process.
• Improved granular control over users.
• Next generation user interface to increase productivity and decrease learning curves.
• Better security and disaster recovery.

Support for an increasing number of participants in the budgeting process.  Rather than creating organizational bottle necks, line managers can access and update numbers they’re responsible for.  Executives and upper management can review summaries and reports as necessary.  This allows the budget owners to focus on developing a practical budget.  Of course, this means fairly advanced control over users and the content they have access is necessary as well.  The current processes require a lot of manual file (and file version) management.  This becomes cumbersome and ultimately impractical with more than a handful of participants.

Improved granular control over users.  As more users become involved in the process, better controls need to be applied.  The existing controls are cumbersome and, although powerful, difficult to master.  A large portion of the design efforts were focused on creating a simple interface to understand who can access what subsets of data and how they relate.  A substantial amount of time is spent setting up these accounts and, depending on how many people are involved, managing changes in responsibility.  I developed a couple somewhat novel approaches to help the budget managers create and understand groups of permissions as well as identify gaps and overlaps.

Next generation user interface to increase productivity and decrease learning curves.  I reevaluated the primary budget interface to reduce clutter and simplify basic interactions.  When I started there were more than three-dozen buttons on a couple toolbars.  I was able to consolidate and simplify the toolbars into a handful of key functions and contextual access to additional tools.  I also simplified the navigation by adopting an iTunes-like navigation.  Many interactions around creating and editing reports were reduced to simple drag/drop motions in a WYSIWYG editor.

Of course, one of the side benefits of a client-server architecture is centralized management of upgrades, backup, recovery, etc.  This improves security and makes it easier for organizations to manage deployments.

I expect the next version of Alight Planning will have a substantial edge on existing budgeting applications.  Supported by a great team working on the underlying engineering problems, the new interface should offer a refreshing alternative to the existing solutions.  It’s certainly an improvement over Excel, which is typically what new Alight customers are coming from.

I worked closely with Brent Pennock (product designer) and Brian Souder (product manager). Our product designs focus on leveraging existing Autodesk technologies across the emerging software as a service (SaaS) distribution channel.

SaaS, strictly speaking, isn’t exactly new. It started to show up in common vernacular (well, common for techies) as early as 2000/2001. SaaS differs from application service providers (ASPs) in many ways, but most notably their architectures diverge. SaaS applications focus on web interfaces using a multi-tenant architecture (multiple people running the same application with virtually separated data, while ASP applications consider web interfaces an afterthought and create individual user instances of each application. I’m certain there are some great articles available on the ‘Net to describe the nuances between these two systems. I suggest starting at Wikipedia.

During the project, Brent and I created several different design concepts across a couple product concepts. The more promising design concepts were fleshed out into fairly robust wireframes after several weeks of customer interviews and paper testing. The next step will include developing a working or pseudo-working prototype, which will be used in usability testing.

Because the project is still in early stages, I don’t want to go into too much detail. First, there are nondisclosure agreements and business plans to consider. And second, I’m not sure what will happen in the next few months as usability testing uncovers flaws in the current design (hopefully there aren’t many of those). Once a beta of the product is released, I’ll speak about it in more depth. Check out Autodesk Labs for more information over the next few months.

UPDATE (2009-05-24):

It looks like Dragonfly is getting some public wings.  Check it out at dragonfly.autodesk.com.

The calculations involved are fairly simple, but (like so many things tax related) require a fair amount of domain knowledge to understand. Unfortunately, accounting tends to be rife with jargon–jargon that is very specific and unforgiving. For example, confusing net revenue (revenue after expenses have been removed) and gross revenue (revenue before expenses have been removed) will generate two very different numbers.

This calculator needed to guide people through the jargon (and avoid it whenever possible), require the minimum information possible, and provide a reasonably useful answer. Of course, it had to do all of this very simply, because the calculator is primarily a marketing piece.

I will include screenshots and a link to the calculator in action as soon as possible. It should be released sometime early Q2 of 2008.

As I’m sure you’re aware, Autodesk is the company behind numerous CAD and 3D rendering applications.  They started with AutoCAD a couple decades ago and have since expanded into specialized CAD programs, BIM programs (like Revit), and general 3D rendering (they acquired 3D Studio MAX and Maya in the last few years).  In fact, AutoCAD is a de-facto standard in most engineering fields.  ProEngineer, TurobCAD, and other competitors basically follow the Autodesk lead when it comes to CAD.  So at least I’m in the right place to make a difference

We’re still in the very early stages of the project and I can’t really talk about it much anyway.  However, it’s a great group of people, so I should at least have fun and learn a few interesting things.

I was pulled in to offer advice and help make some of the bigger UI decisions.  More than anything, I tried to give the main architect and developers a crash-course in interaction design.  I gave them lots of thoughts, but I also tried to help them understand the thought process in UI.  How to approach problems from a user perspective rather than a business or technical perspective.  It’s not as easy as you’d think.  In fact, I believe it’s one of the keystone skills a good interaction designer brings to the table.  Furthermore, I’m not certain this is the kind of skill that can be taught in a book or a series of reproducible steps.

Both Jennifer (architect) and Loren (developer) have excellent instincts concerning interaction and usability.  My fear is they get too much push back from the customers and try to please the end users by adding features rather than solving problems.  A subtle distinction I try to emphasize, but I don’t think it is very obvious sometimes.  It’s very easy to add a widget, change a color, move a button, or create a report because a customer asks for it.  It’s not as easy to fully understand the reasoning for the request and solving the root problem, which frequently has little or nothing to do with the requested feature.  But, I am confident Jennifer and Loren are on the right track for now.  I’ll check in every now and then just to make sure they don’t run into any trouble.

And people say I’m ambitious.  Sojern has set out with a defined goal of creating $1 billion of shareholder value over the next 3-4 years.  Don’t get me wrong, it’s a great group of people with lots of talent.  They’ve got the resources and management with enough business acumen and sales experience to probably pull it off.  However, that’s one hell of a goal to start out with!

If nothing else, Sojern should be an interesting ride.  I’m not convinced the business is ready (maybe in six months) for my skill-set yet; however, I’ll do everything I can in the meantime.  Hopefully, I’m wrong and they will need to develop all of the components currently being discussed in parallel.  I suspect quite a few components and concepts will fall into v3, v4, and v5 discussions, because this project strikes me as substantially larger than most people involved want to admit.  I have been accused of biting too much off at the same time, but I’ve never seen an entire office do it at the same time.  I hope I’m wrong, but it’s hard to not notice some of the signs.

Despite all of this, the monstrous goals, the gargantuan challenges, the short time-line, I still think Sojern will probably succeed.  It is just a matter of time.  Given the collection of experience already in the room and the several million dollars in angel investment already acquired, I doubt it’ll take very long for success to find Sojern.

I enjoyed my brief time at Intuit; however, with rising prospects elsewhere leaving opens up innumerable opportunities I would have either overlooked or bypassed while at Intuit.  There is something to be said for constantly throwing oneself into the raptures of change and chaos.  It might be crazy… or it might be brilliant.  Haven’t decided which just yet

Maybe I’ll still have a chance to work on some of those lingering projects as a contractor in a few months.  And, if nothing else, I learned a few things, made some improvements in a few products, and met some really great people.  Any experience with all of that must have been worth it.

On the plus side, a majority of the people from the office are joining a new startup called Sojern.  I’m not a big fan of the misspelling of sojourn (to have a safe and successful trip or journey); however, the business plan is interesting.  I’m negotiating a part-time contract with Sojern along with a couple other possible clients.

Of course, I have every confidence that the entire group will land on their respective feet without any trouble.  The whole office was comprised of experienced professionals with more than a bit of entrepreneurial spirit.