Marking Fields with New or Unread Data

Up to now in IntelliGantt we've been marking entire rows as unread. Which is good, but considering an IntelliGantt row can have more than 100 custom fields, we thought we could do better. For instance, it might be useful to show which fields changed after a synchronization. It turns out the difference logic we use can do a field-by-field comparison, which means we can do something like this:



You can see the top two rows have unread markers on the left. More subtle is the dark gray circle in the top left of the task display name in row 2. This is the 'unread field' marker. We originally started with a similar 'unread task' marker in the cell, but it turns in to be a lot of yellow and is so vibrant its quite distracting.

The gray circle is not as visually intrusive so you won't lose track of the task data. There's also some interesting things we can do with this as well, such as changing its color when the mouse is over it. We're even thinking of making it behave like a button.

What will it do? Hmm... We have an idea for that.

Building Intuitive UIs

If you've read any of my posts at ReadWriteWeb, you know I love to look at things with an eye towards the past. So many times a new problem is really an old problem. Like User Interface Design.

I came across this video (Introducing the Book) while reading Scott Maxwell's blog. After I stopped laughing, I began to think about our own UI and how well it performs for our customers-- especially for a 'complex' business segment like project management.

In my opinion, we're doing pretty well. In fact, we recently did a screencast to show a few UI niceties we bring to project management. Little things like telling you whether your tasks are to the left or to the right of your current Gantt view. Or showing you why you can't link two tasks together-- highlighting the path that would create the circular link.

But I don't think we've built the most intuitive UI by any stretch. Project Management does have a certain amount of complexity. Connecting business systems to the web is not trivial. However, if you happen to hear from a customer 'That's all you have to do?', then you know you're on the right path.

And we do listen to our customers.

I Resemble That Remark

Anne Zelenka posted a good commentary on her site yesterday regarding her preference for everything to be in the browser. I've been reading Anne's blog for a while now and I respect her opinions, so much so that I asked her to review our soon-to-be-released hybrid application. I hope she reviews it even more now because I think it might just change her mind.

But on to Anne's arguments. Among her points are:

• Most exciting innovations are taking place in the browser


• Browsers are the only way to develop cross-platform


• Browsers go beyond data and integrates information


• Browser experience can be made consistent


• The Browser is about me

Which leads her to predict:

"The browser will be extended to give us offline connectivity and access to desktop resources. The browser and its context provides what we need for mobile access. The browser is where it’s at, not the desktop."

Let's ignore the fact that a web browser is a desktop application for the time being because we should always strive to avoid tautologies. Instead, I believe we can reduce Anne's arguments to:

• Accessibilty


• Personalization

But let's examine Anne's points first.

1. Most exciting innovations are taking place in the browser

I'm not sure if Anne means the browser itself, or the web sites a browser points to. If its the browser itself, then true, there is a battle raging between Mozilla and Internet Explorer, but I disagree that better tabbing and RSS integration represent the pinnacle of innovation.

If its the web sites a browser points to, then I think its a push. This is the classic desktop versus webtop argument which usually reduces to what you prefer for what task. For instance, some people may be fine with Writely, some people may require FrameMaker. I gave GMail a try, I prefer Thunderbird right now. I'll probably test Outlook 2007 when it comes out, or maybe GMail will add some offline support, which is critical for me.

What I will agree with is its easier for people to try out innovation if they can get to it with a browser-- which is why I categorize this argument under Accessibility.

2. The only way to develop cross-platform.

Cross platform development has been one of those holy grails that seem more like the Easter Bunny than an actual chalice. How many cross-platform 'solutions' have come and gone? Anne acknowledges its not Java (totally agree), but there's a whole litany of attempts (anybody remember Galaxy? We almost bankrupted a previous company with that one).

I will agree there are not many choices, but that's because most companies don't want there to be many choices. As long as you have that tension, I doubt HTML will turn into a silver bullet. Because of that tension, codes extensions certainly will not. A Firefox extension will not work with IE or Safari. Same for IE or Safari add-ons. In a sense, web browsers already mirror operation systems in their lines of code demarkation.

Two additional thoughts:

2a. I do think Adobe has a shot at cross platform development with Apollo, though perhaps not so much for the 'classic' browser on the desktop, but for the mini-browser on the mobile device.

2b. I think the other possibility may be .NET. I mention this in an earlier post, but I believe Mono was the major reason Microsoft worked out a partnership with Novell.

3. Browsers go beyond data and integrate information

What about a CRM applications? That seems to integrate a lot of information. Or placing Access data tables within you MS Office documents. Or what about the latest Visual Studio development environment that maintains a rich set of constantly updating reference material online?

Two nice things about desktop applications that are designed to integrate information: a) They understand the information type so you don't have to and b) someone has designed the information layout and flow so you don't have to.

I think the issue here is really about personalization. If you don't agree with how an app lays out information, it can be arduous or impossible to change. Web browsers make it very easy to create your own, personalized mess dashboard.

4. Browser experience can be made consistent

This I just disagree with. Are all blogs consistent? Are all web apps consistent? Hardly. Maybe Anne means consistency in terms of deploying an application to users. In this case, sure, but then its more an accessibility issue (how easy is it to deploy a desktop app versus a desktop app) than an intrisic consistency issue.

5. The Browser is about me

This is Anne's most powerful point. It speaks to what's wrong with desktop software-- or even software in general. And the reason the 'browser is about me' and not the desktop app is because the web application is forced to be simple. Both the newnewss of web solutions and the constraints of the HTML world dictate simple implementations. Desktop applications, on the other hand, have rocketed past human comprehension and make people feel lost in space.

I look at a lot of the online solutions out there and I'm convinced that, while accessibility is appealing, simplicity is the real selling point. Simplicity in what you can do, in how you can personalize and, most importantly, in why one office worker can explain it to another.

I agree wholeheartedly with Anne on this point, but believe its more accidental then designed. And, if the world truly did adopt web applications exclusively, then web apps would complicate themselves so inexplicably that they would no longer be about anyone.


Another Prediction


What do I think the future is? I do think browsers will develop offline capabiity, but the real solution is software that allows for the right tool for the audience. As I said earlier, writers may need FrameMaker to write their books, but an editor would only need a PDF reader to edit it. Architects may need Autocad, but contractors may only need Visio and framers may only need a printout of their wall.

I only see one thing standing in the way-- installation that doesn't involve the user. If the browser can do it, I see no reason why the OS can't; and I'd argue .NET takes us some of the way there. Once that is solved, then installing the right application-- be it desktop, browser extension or web-- will be no different than sending a drawing to a printer. People in different roles need different views of data in different presentations. It will be the ability of *any* software to use desktop, extension or webtop effectively to address the proper presentation for distinct audiences that will determine success in the future.

So what do you think, Anne; would you still like to try my desk/web hybrid app?

MS Project, MindJet, SharePoint and Groove Interconnected

Doesn't seem possible, does it? How can four very different applications work together?

With one unique application.



TeamDirection Project 2007 has the robustness of an athlete, the wherewithal of a concierge and the communication skills of a diplomat. But perhaps most importantly it brings project management to a more human level.

We realize there are people involved in projects. This is why we integrated Instant Messaging right into the project view. We made it behave very similarly to SharePoint integration with MS Office apps so SharePoint (and Groove) users will be right at home.

But the real benefits are for team members who don't need a project management tool. Rather, they just need their browsers to point to SharePoint workspaces. Or if they have the newest MS Office family member, Groove 2007, then join Groove workspaces that take advantage of forms. The important thing is these team members need no additional software to participate in the project and complete their tasks.

We also aim to make the project manager's life a little better too. It's now very easy to move data from MS Project into TeamDirection, and from TeamDirection back to MS Project. Not import/export, but full synchronization. And not necessarily the entire project.

For example, while a project manager may be perfectly at home in a 1000 task project, sometimes its easier for a team to work on smaller pieces. TeamDirection Project lets the project manager identify a summary task as the piece of the project to share. Once in the TeamDirection system, we maintain a link to the summary task's origin and allow it to be published to either SharePoint Task Lists or Groove Task Lists. TeamDirection Project will then gather task data as people update their assigned tasks and synchronize that data with original summary task (and its children) in MS Project. It may sound difficult, but we've got it down to two clicks.

The result is any summary task can become a shared task list.

And not just MS Project summary tasks, but also topics and subtopics. The observant readers may have recognized the simple diagram above as a MindMap. We've found MindJet's MindManager is not only a great way to conceptualize a project but a powerful way to communicate it to a broad audience. TeamDirection Project takes it one step further-- it gives you a simple way to connect projects and tasks to individual team members, through SharePoint and Groove, so you can now execute and track them too.

Finally, we've made a few project management enhancements we're proud of. Things like an improved, interactive Gantt chart and a better Task grid. Useful features like multi-level undo, multi-project views with filtering, a very handy project organizer to group projects and 'smart folders' to quickly identify late ones.

Our philosophy at TeamDirection is 'The Right Tool for the Job.' We could spend years trying to make a project management solution do everything anybody ever wanted. But then it would end up looking something like this.

We believe in the right tool for the job. One of our jobs is making project management easy, accessible and useful. But our other job is to make sure the task data you need is in the application you want. MS Project, MindJet, SharePoint and Groove are a few such applications, but there are many more out there. Most of the world's projects are started with Excel. More and more task lists are executed with next generation web applications like BaseCamp and @Task. TeamDirection helps you make sure your projects are completed with the right tool for the right audience.