2. Princeton Digital
Advisors uses
architectural
techniques to ensure
the problem gets
solved, whether it’s a
long-term legacy
system migration, or a
new cloud-based as-a-
service offering.
These are non-code examples
from recent projects, showing how
we carry the architectural intent
from the business case through to
implementation.
Assessments and program portfolio
techniques
Techniques which understand the customer
better (business architecture)
Techniques to drive risk down in non-
functional ASRs
Techniques which provide guidance to the
implementation team (solution architecture)
9. Helping
people live
better lives
Transform internally
(employee)
New product & subscription revenue via IoT
Social & mobile tools (competitive
draw) for easier onboarding,
ordering; predictable benefits
Crowd-sourced R&D; sentiment analysis
Reliable, easy-to-use global solutions;
best practice sharing
Global “reach” with cloud; integrated
solutions for China
Increase customer loyalty
Create new revenue streams
Drive brand of Contoso
Enable One Contoso
Retain and grow entry-level ABOs
Cross-team collaboration
Sentiment-driven 4P’s & customer
service improvements
Best practice coaching; improved
analytics for building mega-
businesses; leader development
Lower operations costs with COTS,
consolidate suppliers
OpportunitiesGoals Solution Space*Objective
Total experience
(customer)
Renew franchisee
partnership
Double number of Platinum's
Increase ABO productivity
Increase Contoso Sales / Revenue
Focus on growth markets
Externalized applications; easier
business/down-line management
Benefits dependency network
Reduce operational costs
Measured-by KPIs
Employee satisfaction
Campaign effectiveness measures
Employee sat / 360
feedback
Employee engagement
CAPEX to sales ratio
CAC, retained customer order size
Gross profit, operating margin
Net promoter score, online share of
voice
Time to hire, employee churn, training
ROI
Working capital ratio, net promoter score
Operating expense ratio, reduced COGS
Revenue per employee, net revenue
Revenue growth rate (target markets)
* People, process & technology
12. Architectural guidance
• Views in the architectural design phase (ISO 42010)
• Patterns (environment, language selection, models in code)
• Informal or viewpoint guidance after sprints have begun
• Formal ATAM/PBAAM reviews or architectural review of
project under way
• External or partner-led reviews
21. Architectural guidance
• Design patterns (API gateways, full-stack)
• Code best practices (MVC or microservices)
• Views as a result of architectural spikes or experiments
• Guidance on containerization and DevOps pipelines
• Specific views on architecturally significant requirements
29. Brian W. Loomis
Chief Digital Officer and Founder, Princeton Digital Advisors
Brian has over 20 years of management and technology consulting experience
with deep experience in translating the business objectives from the
boardroom into world-class digital products and services. He has served as a
CTO, as an enterprise architect, and as a product designer in several start-
ups, and has created business-driven technology strategies, customer
experience validation, and developed over a dozen innovative digital products
and services.
Brian has consulted with teams in organizations across high-tech, healthcare,
manufacturing, consumer goods and public sector. Brian is a regular
international speaker and a prolific writer within architecture and agile
communities and holds multiple architecture distinctions and technical
certifications. He is an alum from Microsoft, having been on two technical
teams supporting .NET and Azure as they first launched, and has broadened
out to be a trusted advisor for journeys to multiple cloud platforms.
Brian received his Bachelor’s in Electrical Engineering from Princeton
University as well as advanced degrees in business and computer science and
served as an officer in the United States Air Force. Home base for him and his
family is in East Lansing, Michigan.