Profile
I architect information. Here is why and how.
Why: I believe that technology is meant to help drive business outcomes.
How: I focus on basic principles of project management and infrastructure design. IT is a critical component, engaged in every aspect of operations and strategy.
Result: My project teams produce highly effective cross-industry business systems for executive leadership. Simple ROI: People that work together effectively.
I have no secrets
As a leader, I tell you what I think (you’ll be surprised how open I am). That’s not the easy way but it’s the only way. I don’t have a magical method that is more secret and more advanced than anyone else’s. Once my team and I get involved, here is what we typically do:
- We select team members
- We research
- We plan
- We create design concepts
- We make prototypes
- We test
- We launch
- We measure and optimize
The projects I am responsible for succeed because I never get tired of learning and improving. The key to good work is not secrets but good staff. Good staff are what you pay for; having good staff requires:
—A good salary.
—A nice working environment
—Rest.
—Doing work they are qualified for.
For specialist tasks I work with the specialists in my network. These individuals are very qualified and equally expensive.
There are exceptions, but I believe that working overtime as a habit leads to bad work. I don’t believe in:
—work on weekends.
—working crazy long hours.
—last minute initiatives.
—finishing presentations five minutes before the deadline.
History
Starting with small companies in the Hartford, CT area in 2003, I have worked in large industries and have become “…one of the most well-versed & adaptable technology leaders in the industry.” (LinkedIn)
You are one of the only people in twelve years to get (or at least state) that point about my team’s business value.
Want to see more? Take a look at my resumé or curriculum vitae