I’m filing this under lessons learned.

When developing anything for the Web or from any IT perspective, there are two things that need to be considered:

1.) It’s very challenging to develop a digital process where there’s no human process.

It’s not that creating a digital process can’t be done, it’s just that it has to be pursued. When you start developing a Web or IT endeavor it’s all about the process that you’re trying to digitize. So having process map is crucial to developing the workflow for a given Web or IT project.

2.) Sometimes a Web or IT project can’t replace real human contact

Some processes, many processes have the luxury of being able to be replaced by computers. However, there are some that no Web site or computer can replaced. In my business, it’s a beautiful idea to streamline or refine work processes, and it’s a work that I love and look very forward to doing, but sometimes there’s no replacement for human contact. Sometimes, creating a digital process where a human one is needed can hurt the process.

What I’ve learned is that you really have to evaluate the projects, analyze them, and sometimes the best thing to do is avoid digitizing a process, allowing the human process to stand.