Darrell Hawley said something very intrusting in a conference call one day that sparked a lot of thought on my end. We were trying to hash out a decision on a conference call and as a lot of group decisions go it was taking time. Darrell said, “Well let’s pick the default answer and then if we have time to come back to the decision, we can maybe move off that default.” I started thinking about “default answers” and it came to me how brilliant this is. Almost every question in life has a default answer. We just have to identify the default answer and see if it’s palatable. If it is, then we can leave that question alone and focus on those where the default answer is not palatable. Once we answer those questions in a satisfactory way, then we can circle back to the default answers that were just palatable and improve the decisions there. That part alone is worth buying into because it does two things. 1) It frees us up to focus on the questions that we need to focus on rather than spending a ton of time fighting with decisions that we don’t have to make anyway. 2) Just as importantly, it accelerates the decision making process.

You probably already employ this method to a degree. Think about your favorite restaurant. You probably have a favorite meal. Well – that’s your default answer. When I’m in a hurry, I will just go with the default answer whenever I’m ordering food. When I’ve got lots of time, I’ll read the menu and think through the possible answers and possibly choose something else.

Something that’s very important to understand – the default doesn’t have to be very good. You can review it and improve it. Continuing the dinner theme – the default answer for me at most restaurants is a burger with fries. Often, there are much better choices on the menu. However, I default to the burger a lot of times because of time or lack of focus on the menu or something.

Then I started thinking about those repeatable decisions and how we have to make them over and over and over and it burns a lot of cycles. The easy example is paying the mortgage. Is that a question – yes. Every month you have the decision to pay the mortgage and the default answer, if you don’t decide one way or the other, is that the mortgage goes unpaid. Is that default answer acceptable? No but we are forced to make that decision over and over again. Among all of the other questions in our lives, it’s another thing that we have keep on our mind and struggle with. The result of all of this thought is that I’m starting to look for ways that I can apply technology or process to start changing the default answers. This is different from the first part because moving off of the default takes action every time we answer the question whereas changing the default answer to something at least palatable means that you don’t have to take action after that. Applied to the mortgage example changing the default involves setting up online bill pay or something in that vein. Once that’s in place the default answer is that the mortgage gets paid and you have to take action to stop it. At that point it’s a decision that make itself and you don’t have to do anything which frees you up to focus on other things.

After I shared my thought process with Darrell, he posted the “Philosophy of If“. He wants to break it down to code and write things in If statements. I don’t think that it’s that simple.

However, since Darrell is insisting on me codifying the solution – it would be in the form of database lookups. There’s a table of questions and a table of possible answers with a link table between to put them together. Each question has a link to its default answer. Replacing the default requires identifying better answers, injecting them into the database and replacing the link. Writing the code in Ifs assumes that you have a set number of possible answers and that you have identified all of them.

The question table has the following fields:
ID
Question
AnswerNeedsReview

The link table has the following fields:
QuestionID
PossibleAnswerID
IsDefault
SortOrder

The PossibleAnswer table has the following fields:
ID
Answer
FirstAction -> nod to David Allen and “Getting Things Done” (Great book and process that everyone should read)

Any time that you find a new answer, you insert the answer and alter the AnswerNeedsReview to false. Once you have reviewed, sorted and set the default again, the decisions is just made until the next time that the AnswerNeedsReview somewhere.

In conversation, someone brought up a Java WSRP implementation and I thought it was an interesting idea. Web Services for Remote Portlets (WSRP) is an Oasis standard defines a set of interfaces and behaviors that allow you to embed content from as web service on your page but more importantly, it allow that content to be interactive with the web service so it’s more than just pulling the HTML. Clicks and other events funnel back to the origional site so that you don’t have to write the backend processing for those controls. This is an interesting idea so I started looking into it.

I was thinking on what would be required to write one, but it turns out that I don’t have to since there’s already one on GotDotNet for Sharepoint. There you can find the WSRP Consumer Web Part Toolkit and the WSRP Producer Web Service Toolkit.

It’s a facinating idea and I can see real possibilities with it. The question that I have is – has anyone used this yet? How well does it work?

As an Architect, I sometimes attend the Architect school. I’m learning so much that I thought I’d share some of the lessions with you.

First lession: the white board is your friend. Until you accept that and embrace it, you will not be a great architect.

Then as time goes on, we work our way up to actually using the white board. Too often someone jumps right to the whiteboard without the proper background or respect for the whiteboard. The end result is often painful to witness.
We start out slow working with simple lines and work our way up. In this lesson, we work with up to 4 lines.

The graduate classes take whiteboarding to a whole new level where it can almost speak to the audience on it’s own without any words needed.

Someday I’ll get to that level – but it’s a long road.