Outsight Interactive Blog

Need to Repair COM+ to get .NET working again?

Denis — Thu, 28 Jan 2010 12:38:51 -0500

Trying to be a “Good Windows User”, I installed the last few Windows system updates. Unfortunately, I also need to be a “Good .Net Programmer”, and one of the recent security updates made it so that my local machine could not serve up ASP.NET pages anymore. I could surf to HTML pages on “localhost”, but trying to load up any of my local ASP.NET pages caused the WWW Publishing service to stop. The culprit was a conflict with COM+. I tracked it down to an error in the Application Event Log with the following message :

“The run-time environment has detected an inconsistency in its internal state. This indicates a potential instability in the process that could be caused by the custom components running in the COM+ application, the components they make use of, or other factors. Error in f:\xpsp3\com\com1x\src\comsvcs\package\cpackage.cpp(1184), hr = 80070002: InitEventCollector failed”

After trying a few solutions that didn’t work, I found out about the Windows update problem, and an approach to fix it here :
http://support.microsoft.com/kb/315296

I was able to repair my COM+ install using the method from that page. My machine is now telling me (again) that I have an important Windows system update to install, but I think I will hold off for a bit…I have actual work to do.

BLACK, WHITE, BEIGE... LEOPARD PRINT?!

Denise — Fri, 08 Jan 2010 18:14:13 -0500

I first saw it at 9:06PM ET, Wednesday, January 6, 2010, a facebook status posted by a friend that consisted of a color "BLACK" and nothing more. I figured I missed something in her stream and moved on. Then I started to see more colors -- "WHITE", "BLACK" (again)... Humnh, does this have something to do with race?

"HOT PINK", "ECRU", "LEOPARD PRINT"

OK, well, I am guessing this isn't about race. A quick google search and I have my answer -- this (or some derivative) has been spreading virally through the ranks of my facebook friends:

"Write the color of your bra in your status. Just the color, nothing else. And send this on to ONLY women no men. It will be neat to see if this will spread the wings of cancer awareness. It will be fun to see how long it takes before the men wonder why the women have a color in their status.....LOL!"

So far no known breast cancer related organization or charity has claimed this campaign, so I strongly suspect that this is just another internet chain letter and not an example of viral marketing. But as a person in the industry, I am finding it an interesting phenomena to follow and consider.

What worked about it?

Well, the thing that makes facebook fun is the interaction -- nothing gains you interaction like enigmatic or provocative status updates. Its fun to put something out there and get a bunch of responses. Its fun to be coy.
It plays on the "in the know" versus "out of the know". It is fun to feel "in the know" by being one of the first to participate in a trend.
As we all know -- "sex sells", so anything that borders on the intimate, is immediately interesting. I detect amongst my friends that it is fun to indicate to their networks this sense that "there is more to me than meets the eye". As well as a few honest individuals who reveal a sense of disappointment that there *isn't* more to them than meets the eye. It is reminiscent of the PETA campaigns with models and movie stars who would "rather be naked than wear fur". Its titillating (pun intended).
I also see a contingent of folks who have been personally affected by this disease who will do just about anything to try to help the cause. [Side note - it is the earnest caring of this group that makes me get truly angry at all of the email, internet and facebook hoax-sters who choose to prey upon them.]
Lastly, it also plays on the seemingly irresistible cultural draw of anything that sets "girls" against "boys".

Analog Blog?

Denise — Tue, 03 Nov 2009 10:13:53 -0500

This is a short, interesting post that talks about the power of blogging, even if only in analog. The world's only known analog blog

DiningIn solves the problem of group meals

Denise — Wed, 21 Oct 2009 11:53:30 -0400

DiningIn has combined "evite" with their ordering in functionality to solve the problem of organizing group meals. Meal organizers can create an invite, set a per person dollar limit and send the invite allowing people to add their meals to the order themselves. Very interesting solution to a problem that I just now realized I had -- love the ingenuity.
DiningIn

Outsight's Design Challenge 2009

Denise — Tue, 06 Jan 2009 16:16:29 -0500

Inspired by the PhizzPop Design Challenge Boston

As some will remember, a little more than a year ago now, Outsight participated in (and won) the PhizzPop Design Challenge - Boston that was sponsored by Microsoft late in 2007. You can check out both our process and the resulting solution. The big take-away for the team (other than the three XBox 360's, that is) was the intense collaborative team experience that came out of working within the constraints of a three-day contest. In fact, Outsight team members who couldn't participate in the contest felt a little left out. The contest rules limited the teams to three people. So, Outsight has decided to reprise the experience to include our entire team.

Design Challenge Reprise

Next week, the Outsight team is going to stage our own Design Challenge. We will take three days to collaborate on a "Research & Development" project of our own choosing. We'll be trying out new techniques and exploring new processes and innovations without the constraints (and potential risks) of experimenting on client work.

Have a challenge for us?

Although we are busy coming up with challenge ideas of our own, it occurred to us to open it up to the larger community to submit potential challenges to our team. Do you have an interactive problem that you wish there were an elegant solution for? Then submit it to us, but please note:

Do NOT submit ideas that are of a proprietary nature to you (or anyone else) as we plan to keep all rights to anything that we create as a result of this exercise and will likely publish it via our blog, portfolio or other means.
We do NOT promise to choose from any of the ideas that are submitted to us, but will consider them.
IF an idea is selected from those that are submitted, we don't guarantee that we will pursue it in the way that you intended. Our plan is to innovate, so we aren't looking to execute on a "solution" so much as we are looking to "solve a problem".
We make no promises to have a working solution at the end of three days. We'll be aiming for a solid, cohesive concept (or several) or perhaps even a prototype.
We make no promises that current technology necessarily supports the solution that we come up with. Although we are definitely based in reality, some times you have to dream a little bit to innovate.
Although it is our intent to share the results, we don't promise that we will do so.

Lessons learned this week at UI 13

Denise — Thu, 16 Oct 2008 23:57:03 -0400

Kelly and I had the opportunity to attend UI 13, put on by Jared Spool's group User Interface Engineering. It was a great conference, full of interesting ideas to share and try. While it is still in my mind, I thought I would share a few of the lessons I learned this week.

In no particular order...

To have a successful design, you have to connect to a clear strategy. (learned from Peter Merholz)

Strategy is about "fit" (learned from Peter Merholz)

"User-centered design NEVER worked." (Jared Spool) [This one deserves some explanation -- Jared's explanation -- Many great designs weren't user-centered. Many user-centered design processes have created less than successful products. There is no evidence that user-centered design ever improved market acceptance. Jared stated that for each of the success stories they examined there were a myriad of reasons that the projects were successful, so could not be attributed to user-centered design alone. If you think you have an example of user-centered design *alone* improving market acceptance, twitter it to Jared. I can't believe they don't exist, but trust him when he says his group found no examples.]

The most successful teams generally do not have a formal methodology. Instead, they tended to have a toolbox of "techniques" and "tricks" that can be applied as appropriate to the situation at hand. (learned from Jared Spool)

"Should we do one long form or multiple shorter forms?"

Denise — Thu, 17 Jul 2008 21:27:08 -0400

"Lowering the barrier of entry" should not be equated with "one form or many"

When considering registration/sign-up with clients, there is a spectre floating about the room, the "Lower the barrier of entry in order to prevent drop-offs" spectre. This is a very good thing. Just ten years ago, I remember being told in no uncertain terms that we had to "force" users to give us as much information as possible. What is interesting to me now though, is that this "how to lower the barrier of entry" question has started to become synonymous with "should we do one long form or multiple short forms".

Don't Lose Sight of the Single Most Important Principle

Before I give my answer to that question, I would like to take a moment to remind folks that the single best way to lower the barrier of entry is to -- ask only for the absolute minimum amount of information you need. Honestly, every other form consideration is secondary to that single guiding principle.

Think you already are? Try looking again. Or have a relative or neighbor look with you. None of my relatives create websites. They are very helpful for seeing sites with fresh eyes..

Common Reasons Folks Use Form Processes

Now, back to one form versus multiple.... Let's start by looking at the thinking behind using multiple short forms rather than one longer form.

Finally, the official word on "OK - Cancel" or "Cancel - OK"

Denise — Tue, 27 May 2008 14:22:37 -0400

I have often been asked by clients about the better order for the OK and Cancel buttons. Finally, Jakob Nielsen has published an 'official' answer To sum up:

Either is perfectly fine.
The question is not of great concern as neither poses a big threat to usability.
If you need a tie-breaker, go with the platform convention that most of your users are known to use.
Generally on the web, most users are on Windows, so "OK" then "Cancel" is the platform convention to follow.

Lastly, and perhaps, most importantly, he points out:

There are questions in usability that are, perhaps, not worth the time spent debating them

The Struggle to Keep Things Simple

Denise — Wed, 14 May 2008 13:45:45 -0400

Have you ever read something that resonates so loud to your experience that you want to run around and share it with everyone you know? I found such a passage today in Jared M. Spools "UIEtips: 4 Design Lessons from the Flip".

"We want to make designs simple, but we don’t want to make them dumb. There’s a difference. The goal is to simplify the design by keeping only the most valuable bits, eliminating everything else.

This is not easy to do. You really have to know something about the users, what they are trying to do, and how they go about doing it. Just having that information will likely push the team to add more features, not less, so you then need a solid vision of how simplicity will make it better. Finally, you have to be ruthless and stubborn, cutting all the unnecessary bits out and sticking to your guns about keeping to the essentials." -- Jared M. Spool

Honestly, I have nothing really to add... Amen...read more...

So you want to be more creative

Jon — Mon, 12 May 2008 10:36:51 -0400

So you want to be more creative, in art, in business, whatever. Check out Hugh MacLeod’s excellent post on being creative.

1. Ignore everybody.
The more original your idea is, the less good advice other people will be able to give you.

2. The idea doesn’t have to be big. It just has to be yours.

3. Put the hours in.
Being good at anything is like figure skating- the definition of being good at it is being able to make it look easy.

4. If your biz plan depends on you suddenly being “discovered” by some big shot, your plan will probably fail.

5. You are responsible for your own experience.

6. Everyone is born creative; everyone is given a box of crayons in kindergarten.

7. Keep your day job.

8. Companies that squelch creativity can no longer compete with companies that champion creativity.

9. Everybody has their own private Mount Everest they were put on this earth to climb.

10. The more talented somebody is, the less they need the props.

11. Don’t try to stand out from the crowd; avoid crowds altogether.

12. If you accept the pain, it cannot hurt you.

13. Never compare your inside with somebody else’s outside.

14. Dying young is overrated.

15. The most important thing a creative person can learn professionally is where to draw the red line that separates what you are willing to do, and what you are not.