Technology Decision Review
Independent view of a proposed solution - problem framing, assumptions, alternatives, and consequences.
Technology Strategy Advisor
Complex Systems · Technology-Enabled Problem Solving
I help leaders solve complex technology and systems problems.
I work across business processes, people, software, data, AI, and architecture to understand what is driving the problem and define the technology direction that best supports the business objective.
Founders · CEOs · CIOs · CTOs · COOs · Leadership Teams
About
Why this perspective is useful
I work where business objectives and complex technology or systems decisions intersect. The starting point is the outcome the organization needs - not a preferred platform, architecture, AI model, or implementation method. Once the objective is clear, I examine how the system behind the problem actually works before deciding what should change.
Enterprise technology
Hands-on experience with enterprise platforms, software, infrastructure, observability, AI/MLOps, authentication, cloud and on-prem systems, and architecture.
Systems thinking
Looking across process, people, information, software, data, decisions, and architecture - rather than treating an application in isolation.
Founder / operator experience
Product, technology, architecture, partnership, prioritization, and resource decisions where consequences are real.
Research & academic perspective
Emerging research in human-AI systems, cognition, decision-making, enterprise systems, and decision support - labeled as emerging, not established proprietary doctrine.
Strategy before implementation
Recommendation first
Primary work is understanding the objective, evaluating options, and defining system or technology direction before major implementation begins.
Advisory work is recommendation-led and delivery-agnostic. Where an affiliated organization could participate in implementation, that relationship is disclosed and the client remains free to choose any delivery partner.
Next
Problems I work on
Situations where process, people, software, data, AI, and architecture interact - and the right direction is not immediately obvious.
View ProblemsExpertise
Complex problems I work on
Bounded problems at the intersection of process, people, decisions, information, software, data, AI, and architecture - especially when the right technical direction is not obvious.
01
Complex process & system problems
Operations involve multiple teams, systems, manual steps, or unclear ownership - and local fixes are not fixing the whole.
- What outcome needs to improve?
- Is the constraint process, software, data, architecture, people, or governance?
- Are we optimizing components while the overall system stays inefficient?
02
Technology-enabled process redesign
An existing process needs to be rethought - not simply digitized in its current form.
- What should the future operating flow look like?
- What should software handle - and what should remain human?
- What information must move between teams and systems?
03
AI & human work design
Leadership wants AI in real operations, but where it should assist, recommend, or automate is unclear.
- What outcome should AI improve?
- Where must humans retain authority?
- How should AI fit existing workflows, data, and systems?
04
Architecture & integration complexity
Individual systems may work, yet the overall operation remains fragmented or slow.
- Why are systems creating friction?
- What should be integrated, centralized, or left independent?
- What does this architecture make harder later?
05
Build · Buy · Integrate · Partner
A capability is needed, but the right implementation model is not obvious.
- Build, buy, integrate, partner, modernize - or wait?
- Are we buying a capability we should own?
- Which option preserves future flexibility?
06
Modernization & transformation
Legacy systems or accumulated complexity may be restricting growth or operational effectiveness.
- Is replacement actually necessary?
- What can remain, integrate, or modernize around the existing system?
- Is technology really the constraint - and what should change first?
07
Independent technology decision review
A solution is already proposed, and leadership wants an independent view before committing.
- Are we solving the right problem?
- Which assumption could make this recommendation wrong?
- What alternatives were set aside - and what constraints will this create?
In practice
How common situations are approached
When a process is slow
Do not immediately automate it. Determine whether the constraint is process design, decision-making, information availability, integration, software, human workload, or architecture.
When leadership wants AI
Do not begin with a model. Determine what outcome should improve, where AI fits the workflow, what data exists, what remains human-led, how AI integrates with the operating system, and how success will be measured.
When a legacy platform causes frustration
Do not automatically recommend replacement. Evaluate what is failing, what should remain, what can be integrated or modernized, and whether replacement would genuinely improve the outcome.
How I think
Understand the system. Identify the constraint. Evaluate the options. Define the direction.
Business outcomes first. Technology in service of strategy. Once the objective is clear, map how the system works, find what is actually blocking the outcome, then decide what technology should - and should not - do.
01
Business outcome
What needs to improve - and why does it matter commercially or operationally?
02
System understanding
How people, processes, decisions, information, software, data, and architecture work together today.
03
Constraint
What is actually preventing the desired outcome - separate symptoms from causes.
04
Options
What realistic alternatives exist - including redesign, integration, automation, AI, architecture change, or leaving part of the system alone.
05
Technology role
What should software, AI, automation, integration, or architecture do - and what should remain human?
06
Trade-offs
Cost, risk, time, complexity, readiness, scalability, dependencies, and reversibility.
07
Direction
What should happen first, next, and later - before major implementation begins.
Working principles
- Business outcomes first. Technology in service of strategy.
- The starting point is the outcome - not a preferred platform, model, or vendor.
- A technically correct solution can still be the wrong system decision.
- Before automating a process, ask whether the process itself should change.
- AI should fit human judgment and operational reality.
- Architecture decisions shape what can change later.
Ways to work
Engagements
Focused on clarity before commitment - objective, system, options, and direction.
Complex System Assessment
Map people, process, decisions, information, software, data, and architecture to identify the real constraint.
AI & Human Work Design
Where AI should assist, recommend, or automate - and how it fits workflows and decision rights.
Architecture & Integration Direction
What to integrate, centralize, modernize, or leave independent given the business objective.
Build · Buy · Integrate · Partner Review
Evaluate implementation models before committing to a path or long-term dependency.
Perspective
A complementary view on a bounded problem
You bring industry knowledge, operational experience, and authority. An external systems perspective can surface options, constraints, and consequences that are harder to see from inside.
Outcome before technology
Start from what needs to improve - not from a preferred tool, model, or vendor roadmap.
Evidence over trends
Direction based on operating context, constraints, and trade-offs - not fashion alone.
Grounded in real systems
7+ years across enterprise technology, research, and founder/operator work - so direction reflects what organizations can operate.
7+Years in enterprise technology, research, and founder/operator work
600+Engineers enabled on a shared monitoring platform
~50%Reduction in on-call alerts
99%Uptime on critical environments
Insights
How I think - selected notes
Direct analysis of systems constraints, AI and human work, architecture, and build/buy/integrate choices - not a general technology blog.
Why AI strategy must begin with business architecture
AI + Human SystemsContact
Discuss a complex technology problem
If your organization is facing a difficult technology, AI, architecture, process, or systems problem, share the context. The first step is understanding the objective and the system behind the problem. I respond within 48 hours.
For founders and senior business or technology leaders responsible for complex systems, technology, AI, or process decisions.
Phone+94 77 363 8063
Scheduletopmate.io/pasindu_bandarigoda
Questions
Common questions
What kinds of problems do you work on?
Problems where business processes, people, decisions, information, software, data, AI, and architecture interact - particularly when the right technical direction is not immediately obvious.
Who do you work with?
Founders and senior business or technology leaders responsible for complex systems, technology, AI, or process decisions.
Do you provide implementation?
Primary focus is problem definition, systems analysis, technology direction, and decision support. Implementation can follow once the direction is clear. If an affiliated company could participate in delivery, that relationship is disclosed.
What does an engagement produce?
A clearer view of the business objective, the system behind the problem, the main constraints, options, trade-offs, and a practical technology-enabled direction.
How do we begin?
Share the problem context, email directly, or schedule a conversation.