Tridev Solutions

Honestly, the application and usage of IT services are limitless. Besides the traditional services for the enterprise, IT can add major value in the following areas: - Promote the nonprofits’ mission and organization value in a broader context - Reach out to it’s primary stakeholders, including the beneficiaries, customers and volunteers (if applicable) with consistent messages for today and tomorrow - Perform statistical analysis and effectiveness of the work programs using AI and BI - Create and publish short, mid and long-term roadmap for the organization - Create B2B synergies as part of a larger transformation opportunities

What’s in a Name? - Enterprise Architect, Solutions Architect, Project Architect, Cloud Architect, ..... During my 44 years career, I have always been focused on “roles" rather than “position” or “job title”. Early catalysts that shaped my young mind in the 80’s were John Zachman’s “The Zachman Framework for Information Systems Architecture” and James Martin’s “Information Engineering”. I was indoctrinated by Dr. Stephen R Covey, author of the famous “The Seven Habits of Highly Effective People” in 1993. He coached and taught me the “absolute must” leadership competence to challenge the status quo and start looking into any technology initiatives in real business terms - “Doing the Right Things”. I have come across many different types of architect positions (by title but not by their roles/actions) - EA, SA, PA, AA, DA, BA, IA, Cloud architect, Cybersecurity Architect, Security Architect, Infrastructure Architect, Network Architect, and many more. Is there a standard definition of these titles/job positions? Not really! I received a call last week from a recruiter, looking for an Enterprise Architect. I asked for some clarity on roles of the EA; I summed up the primary job responsibilities, as follows: project management, meeting coordination, business requirement analysis, documentation, and then a superstar. Has the importance of Enterprise Architect somehow diminished over the years? Everyone is trying to be creative in bringing talents at any cost. The roles and responsibilities are becoming more and more blurry- sometimes meaningless! As a result, the business wing of the enterprise is getting more and more confused. (Don’t take me wrong! I have worked for companies that do fairly good job in creating the business vision, strategy, architecture roadmap and tactical implementation plan in collaboration with business and technologies SMEs. Here are some of the key messages that I would like to share: For EA and Technologies: · Customer is the reason that we, in Technologies, exist · Practice architecture in close collaboration with business · Create mass awareness at all levels of the organization · Educate business in simple “business terms” · Delight them by providing premium service and exceptional leadership · Win their trust by improving key business results · Establish shared/joint Enterprise Architecture goals with business For Business: · You are the ones fueling business growth, transformation and innovation · Transform your business effectively to keep up with the rapid digital transformation by active engagement with EA and Technologies teams · Establish clear roles and responsibilities · Demand effective, quantifiable and measurable business metrics from EA · Establish shared/joint business goals with Enterprise Architecture References: 1. “The Zachman Framework for Enterprise Architecture” – John A Zachman 2. “Information Engineering” – James Martin 3. “The Seven Habits of Highly Effective People” – Stephen R Covey.