Recognize strengths and weaknesses in a solution
One challenge that a solution architect faces is becoming so close to
the solution that they proposed or designed that they don't reflect on its
strengths and weaknesses. Therefore, at key points during the project,
it's a good idea to pause and assess what you are designing. Optimally, you should
ask another architect to help in this assessment; likely, you might find that you are asked
to do the same.
Address organization objectives
A project's key objectives shouldn't be so extensive that you can't perform individual checks to ensure that you're addressing them. Additionally, you should reflect on how well you've addressed the objectives, making sure that more information couldn't be added to better highlight how your solution will meet the customer's needs. Occasionally, another architect might have a creative alternative that could be worth including, or they might be able to identify whether you've included items that don't provide value toward your goals and are therefore nonessential.
Over-solving a problem
Periodically, architects like to solve problems with solutions (apps) that they are comfortable with. Review your proposed solution components to make sure that you haven't proposed an app or prebuilt solution that is disproportionate to the needs.
Customize an app vs. using a prebuilt app
If you have larger parts of the solution that are specified as custom-built components, determine whether any parts might be better suited for an existing Dynamics 365 or AppSource app. Especially during the presale timeframe, proposing a solution with a few options is an excellent way to talk through the positive and negative aspects of each approach with the customer.
Compare your proposed solution with the competition
While it might be optimal being the only partner who is asked to propose a solution, it is likely that multiple options are being evaluated simultaneously. During the presale review of your proposed architecture, consider analyzing how your solution compares with others. You will likely face competition from others who are proposing Microsoft solutions and from similar competitive vendors as well. Being prepared with questions about your competition and preparing your other sales team members for how to compare your solution with the competition can be helpful.
Organizational opportunities
During the discovery phase, your customer likely shared some of their other organizational challenges. When your proposed solution is in place, review those challenges to determine whether any could be added to the scope of your proposal as easy wins.
Irrelevant system rebuilds
Occasionally, organizations need to move from existing, antiquated systems toward more modern technology. With current changes in technology, rapid advances in artificial intelligence, higher speed, and increased capacity, advancing to a modern system is a significant change that can be reimagined. Assess your proposal to make sure that you have not unintentionally rebuilt the aging system that your customer is moving away from.
SWOT analysis
Periodically during a project, you will likely participate in the creation of a Strengths, Weaknesses, Opportunities, and Threats (SWOT) analysis. This analysis can be detailed or casual. After you've intentionally completed a few of these analyses, you might keep a mental list of each of these processes as the project progresses.
A brief SWOT analysis for Woodgrove Bank might resemble the following example:
You can use the knowledge you've gained from a SWOT analysis to help guide your project and decisions for a better outcome.
Exercise: Identify risks for Woodgrove Bank
As you've continued learning more about Woodgrove Bank, a few risks have presented themselves. Review all risks that you've identified so far about Woodgrove Bank and determine the solution that they need.
List at least five risks Woodgrove face with implementing a successful solution
Consider the following questions, which can help generate ideas for your list of five risks:
Does this project have any non-tangible risks?
What direct or indirect competition does Woodgrove Bank face?
Does your firm possess the skills to complete the job for Woodgrove Bank?
Is the timeline realistic?
Is the budget realistic?