Architects are often introduced after a project has already been sold, funded, and approved. By that stage, major assumptions may already have been made regarding scope, complexity, timelines, and delivery approaches.

 

In my experience, involving architects earlier can significantly improve project outcomes.

 

Architects bring a practical perspective that complements sales and delivery discussions. They can identify implementation risks, clarify assumptions, assess platform implications, and ensure proposed solutions align with enterprise architecture principles.

 

Early involvement does not mean architects need to participate in every customer conversation. It means ensuring architectural thinking informs key decisions before commitments are made.

 

This becomes particularly important for large ServiceNow programmes involving multiple products, integrations, and transformation objectives. Small misunderstandings during the sales phase can create significant delivery challenges later.

 

Architects can also help identify opportunities customers may not have considered. Their broader platform perspective often reveals more sustainable approaches than simply implementing the stated requirements.

 

When architecture is engaged too late, teams frequently spend time correcting assumptions that could have been addressed earlier.

 

The most successful engagements create continuity between sales, solutioning, and delivery. Architecture plays an important role in maintaining that continuity and ensuring commitments remain aligned with technical reality.

 

Ultimately, architects should not only help design solutions. They should also help shape them from the very beginning.