Example Achievement Log for a Solutions Architect

Software & IT

Example Achievement Log for a Solutions Architect

This Solutions Architect spent the year designing infrastructure for mid-market cloud migrations and handling the customer friction that comes with them. You'll see technical delivery alongside the unglamorous work of stakeholder pushback, scope creep, and the moments when a design doesn't survive contact with a customer's actual network.

A year in the life of a Solutions Architect's log

  • Feb - task: Picked up the Meridian Bank RFP after Dave left. Their on-prem Oracle setup was undocumented; spent three weeks reverse-engineering network topology from firewall rules and DNS logs.
  • Mar - achievement: Delivered Meridian's AWS migration design: hybrid setup with direct connect, three-tier app layer, RDS multi-AZ. Cut their TCO forecast from $2.1M to $1.3M over five years. Customer signed a 2-year extension.
  • Apr - feedback: Meridian's CTO said in the kick-off: 'You actually understood our disaster recovery nightmare instead of just throwing redundancy at it.' Rare compliment from someone who's seen ten architects.
  • Apr - task: Ran technical deep-dives for Prescott Manufacturing. Their procurement team demanded we justify every API call and database lookup. Redesigned docs to map to their cost-tracking requirements instead of my usual cloud-native pitch.
  • Jun - achievement: Prescott signed off on $900K engagement. Their finance sign-off went from three weeks of back-and-forth to a single meeting after I restructured the cost model to their GL structure.
  • Jul - task: Discovered our standard Postgres to Aurora migration pattern breaks their in-house app's reliance on custom ltree functions. Had to architect a three-month hybrid phase instead of the planned cutover.
  • Jul - achievement: Completed Prescott's phased cutover with zero unplanned downtime. App performance improved 23% in QA environment. Finance team used it as proof point for two additional modernization projects.
  • Sep - feedback: Prescott's infrastructure lead told my manager: 'Most architects disappear after sign-off. He stayed through the nightmare phase and didn't blame us for not reading the fine print.'
  • Oct - task: Architected VPC segmentation policy for Sentinel Healthcare. Their compliance officer's concerns about lateral movement across 47 applications meant designing six separate network layers with strict peering rules.
  • Oct - achievement: Delivered Sentinel architecture. Design passed their third-party penetration testing without remediation findings. Compliance audit time dropped from estimated eight weeks to four days.
  • Dec - task: Started design review process for the Q1 pipeline. Built a rubric to catch scope creep earlier, learned the hard way this year that ambiguous requirements cost us more in rework than in upfront conversations.

What makes a strong entry

What most people write: Delivered Meridian's AWS migration design and saved them money.

What went in the log: Delivered Meridian's AWS migration design: hybrid setup with direct connect, three-tier app layer, RDS multi-AZ. Cut their TCO forecast from $2.1M to $1.3M over five years. Customer signed a 2-year extension.

The strong version includes the actual technologies chosen, the specific financial before/after, and the business outcome (contract extension), so six months later you can point to exactly what you built and why it mattered to the customer.

What most people write: Handled a difficult customer migration with some unexpected issues.

What went in the log: Discovered our standard Postgres to Aurora migration pattern breaks their in-house app's reliance on custom ltree functions. Had to architect a three-month hybrid phase instead of the planned cutover.

The strong version names the specific technical constraint (ltree functions), what the standard approach assumed, and how you changed course, making it credible and memorable rather than a vague admission that something went wrong.

How this becomes your review in November

This year I delivered four major architecture engagements totaling over $3.5M in customer commitments, with a focus on understanding the actual business constraints behind technical requirements rather than imposing templates. The Meridian Bank project demonstrated the value of reverse-engineering their undocumented on-prem setup before designing the migration: the design cut their five-year costs by 37% and earned a contract extension. I also learned that scope creep often signals a gap in requirements conversation, not a customer problem, restructuring the Prescott engagement around their cost-tracking practices shortened their finance approval from weeks to days and unlocked two follow-on modernization projects. The pattern holding across the year was picking up the less visible work: staying through phased cutover phases, designing VPC segmentation for compliance edge cases, and rebuilding documentation to map to how customers actually track costs.

Starting your own log

Don't try to reconstruct a year you have already had. Start from today, one line whenever something happens, and let it build. The Perform Review Achievement Log does this for you and can capture wins straight from Slack, and how to start an achievement log covers the wider playbook.

Example Logs for Related Roles

Ready to start your own? Start your Achievement Log free, see how the Perform Review Achievement Log works, or browse performance review phrases for Solutions Architect.