The Principles Behind Successful IT Projects
When people think about successful IT projects, they often picture clever software, modern technology or talented programmers. While these are certainly important, they are rarely the deciding factors.
After more than 25 years working in information technology, I’ve found that successful projects are usually built on something much less glamorous—good planning, clear communication, shared responsibility and professional integrity.
Technology changes constantly. Sound business principles do not.
Projects Are a Partnership
Every project involves at least two parties: the service provider and the client. Both have responsibilities, and both contribute to the outcome.
A project works best when expectations are clear from the beginning. Tasks are agreed upon, responsibilities are understood, decisions are documented and realistic timeframes are established.
Problems usually begin when these simple principles start to break down. Missed deadlines, changing requirements, forgotten decisions, poor communication or a reluctance to take ownership can quickly place unnecessary pressure on everyone involved.
Successful projects are built on trust. Trust grows through reliability, transparency and a willingness to work together towards the same objective.
Planning Is Where Success Begins
People often see the finished product without appreciating the work that took place beforehand.
In reality, many successful IT projects appear straightforward because so much effort was invested in planning.
Before development begins, there needs to be a clear understanding of the business, its goals, the people who will use the solution and how success will be measured. A good solution is about far more than writing code. It considers how the entire system will function over time.
Questions worth asking include:
- Is the solution easy for people to use?
- Does it guide users naturally through their tasks?
- Is data entered accurately and consistently?
- Will it perform well as demand grows?
- Has security been considered from the outset?
- What happens if hardware fails or data is lost?
- Is there sufficient documentation for future support?
Good planning reduces risk. It also reduces expensive surprises later in the project.
Best Practice Is a Habit
Technology never stands still. New techniques emerge, standards evolve and better ways of working are continually discovered.
For that reason, best practice is not a fixed list of rules. It is an ongoing commitment to learning.
Professional development may come through industry conferences, workshops, technical papers, mentoring, peer review, vendor documentation or simply learning from experienced colleagues. Every worthwhile project teaches something that can improve the next one.
Sometimes this also means recognising when older approaches are no longer the best solution. Experience helps us distinguish between methods that continue to serve us well and those that should be left behind.
Remaining current is part of being professional.
Communication Is a Professional Skill
Many technical problems are, at their heart, communication problems.
Clients do not expect every answer immediately. They do expect honesty, responsiveness and confidence.
Some simple practices make a significant difference:
- Return phone calls and emails promptly.
- Be realistic about timelines.
- Admit when further investigation is needed.
- Avoid making commitments that cannot be delivered.
- Explain technical matters in language the client understands.
- Keep clients informed throughout the project.
People generally appreciate openness far more than false certainty.
Good communication builds confidence long before any software is delivered.
Ownership Matters
No project is perfect.
Unexpected issues arise. Requirements evolve. Occasionally mistakes are made.
What distinguishes experienced professionals is not the absence of problems, but how they respond when problems occur.
Taking ownership, communicating openly and working collaboratively towards a solution builds trust. Hiding mistakes, shifting blame or avoiding difficult conversations almost always creates larger problems.
Clients understand that technology is complex. What they value most is confidence that the people managing the project will deal with challenges honestly and professionally.
Technology Supports Business
One mistake sometimes made within the industry is focusing on technology for its own sake.
Businesses are not purchasing software simply because it is technically impressive. They are investing in outcomes.
The objective might be improving customer service, reducing manual work, increasing efficiency or providing better information for decision-making.
Technology is simply one of the tools used to achieve those goals.
Keeping the business objective in view throughout the project helps prevent unnecessary complexity and ensures the final solution delivers genuine value.
Experience Develops Judgement
Technical knowledge is important, but experience develops judgement.
Over the years I have invested considerable time learning new technologies, only to discover later that some were not suitable for long-term use. While that may appear to be wasted effort, it never truly is. Every experience contributes to better decision-making.
Equally, there are technologies I have deliberately chosen not to pursue because they were outside the areas where I could provide the greatest value to clients.
Professional maturity is not about knowing everything. It is about understanding your strengths, recognising your limitations and continually improving your skills.
Never Stop Learning
One lesson has remained consistent throughout my career.
Growth comes from being willing to tackle new challenges, learn unfamiliar skills and occasionally work through difficult problems that initially seem beyond reach.
Not every challenge should be pursued, but avoiding all challenges inevitably leads to stagnation.
The most capable professionals I have worked alongside have shared one characteristic: they never stopped learning.
Final Thoughts
Successful IT projects are rarely defined by technology alone.
They succeed because people communicate well, plan carefully, take ownership of their work and continue developing their knowledge throughout their careers.
The software eventually reaches production, but long before that happens the foundations have already been laid.
Technology will continue to change, just as it always has. The principles behind successful projects, however, remain remarkably consistent.
Those principles are worth investing in—for every project, every client and every professional who wants to leave behind work they can genuinely be proud of.
Lessons from Experience
Over the years, I’ve found that some of the most valuable lessons came from real projects rather than textbooks. Here are a few examples that reinforced the principles discussed above.
Sometimes the Right Decision Is Not to Continue
On one occasion I spent many hours learning a new analytics platform because it appeared to offer worthwhile capabilities for clients. After investing significant time, I realised the software was introducing more problems than it solved. Rather than continue simply because of the effort already invested, I chose to walk away and use a different solution.
It reminded me that experience is not measured by how much time we spend on something, but by recognising when a better path exists. Walk-aways are however rare, but they have occurred.
Pre-planning Saves Time Later
Many clients are eager to begin development immediately. Understandably, they want to see progress as soon as possible.
However, projects that begin with careful discussion of requirements, business processes and future growth usually progress far more smoothly than those rushed into development. Time spent understanding the business almost always saves considerably more time during implementation.
Good planning rarely attracts attention, yet it is often the reason a project appears to run effortlessly.
Learning Never Stops
Early in my career I became fascinated with understanding computers at a very low level. One exercise involved printing the hexadecimal code for an Apple II computer and writing a simple hard disk read/write routine directly in machine code.
It certainly wasn’t the easiest way to learn, but it taught me how computers really worked beneath the operating system. That curiosity has stayed with me throughout my career and continues to influence how I approach problem-solving today. We seem to have a curiosity and intuitive drive, as compared to people I have met who consider these efforts as waste of time. It is not.
Technology Changes. Principles Don’t.
Over the years I’ve worked with technologies that were once regarded as essential but have since disappeared, while others have evolved beyond recognition.
The specific software has changed many times.
The principles that deliver successful projects—careful planning, clear communication, ownership, continual learning and genuine concern for clients—have remained remarkably consistent.
That is perhaps the most valuable lesson experience has taught me.
More Lessons from Experience
Sometimes Persistence Pays Off
Early in my career, someone told me I would never work with computers professionally. Later, another person confidently assured me I would never work with IBM.
Neither prediction proved correct.
Those experiences taught me not to place too much weight on the limitations other people place on us. If we continue learning, seek opportunities and remain prepared to put in the effort, our future is often determined more by our persistence than by someone else’s opinion.
It also reminds me to be careful about discouraging others. We rarely know where another person’s determination may take them.
Finding the Right Niche
There are countless areas within information technology. No one person can master them all.
At one stage I deliberately chose to focus on complete website solutions for small businesses and community organisations. Rather than trying to become an expert in every technology available, I concentrated on delivering reliable, end-to-end WordPress and AWS hosting solutions that clients could depend upon.
That decision taught me that success often comes from knowing where you can provide the greatest value, rather than trying to do everything.
There will always be specialists who know more in their particular field. Working collaboratively with others is often a strength rather than a weakness.
The Cost of “Just One Small Change”
Almost every project reaches the point where someone says, “Can we just add one more small feature?”
Often the request itself is perfectly reasonable. The difficulty is that every change has consequences.
A seemingly simple addition may require changes to design, programming, testing, documentation, user training and project timelines. Sometimes it introduces new risks that were not present before.
This doesn’t mean changes should never be made. Good projects remain flexible as business needs to evolve. However, successful projects also recognise that every change should be considered carefully so that expectations, costs and delivery dates remain realistic.
Managing change isn’t about saying “no”. It’s about helping everyone understand the impact of saying “yes”. I have always factored in an ability for a degree of flexibility. This has been a problem for fixed project design systems and teams that do not wish to include flexibility at certain milestones of a project. I have included this in the actual specifications where it was really needed as part of the design methodology.
