Skip to content
Skip to lifecycle

MY ROLE · END-TO-END DIGITAL DELIVERY

Across the
delivery lifecycle.

From business need to production, I connect the decisions in between by shaping direction, owning architecture and leading teams toward dependable delivery.

THE LIFECYCLE AT A GLANCESelect a stage to explore my role
DELIVERY LEADERSHIP THROUGHOUTScope · Priorities · Teams · Dependencies · Risk · Quality · Releases
Delivery leadership runs across every stage. The journey is iterative, with quality built in throughout.Operate → Learn → Back to discovery
01 / EXPLORE MY CONTRIBUTION

The role. The decisions. The work.

ROLE PERSPECTIVE

One connected practice: architecture and delivery leadership, grounded in UX and hands-on engineering.

PROJECT PERSPECTIVE

Explore my connected practice, then choose a project to see its specific remit.

Solution architecture. Leadership

STAGE 03 / 08OWN

Solution architecture

Translate business, product and technical requirements into a solution teams can implement, with explicit decisions and trade-offs.

Decisions I shape or own

  • Where are the solution boundaries, and which architecture style fits?
  • What should we build, reuse or buy, given cost, risk and time?
  • How do APIs, data, integrations and identity work together?
  • Which trade-offs meet performance, security, availability and delivery constraints?

What I deliver / define

Solution views / C4Architecture decisions (ADRs)NFRs & trade-offsIntegration / API designArchitecture roadmap

Skills supporting this stage

Solution modeling · Modular architecture · API contracts · IAM / RBAC · Cloud & data design

Experience behind this

Marsad (NIMIC): Angular/Nx architecture, SSR, API and BI integration, and headless CMS modernization. Hisn: end-to-end solution design.

Ask Ahmed about this stage

Copy this question, then paste it into Ask Ahmed.

Open Ask Ahmed
CONNECTED, NOT SEQUENTIAL

Architecture evolves with discovery. UX informs engineering. Quality starts before the first commit. Delivery leadership connects teams, dependencies and decisions throughout.

Read the complete lifecycle

All eight stages, with the responsibilities and outputs that connect the practice.

01 · Business & discovery

Turn business objectives, stakeholder needs and constraints into a clear problem and delivery direction.

Decisions I shape or own

  1. Which business outcome matters, and how will we measure it?
  2. What belongs in scope, and which constraints shape the solution?
  3. Which processes and capabilities need to change?

What I deliver / define

  • Problem statement
  • Capability / process map
  • Scope & constraints
  • Success measures

Skills supporting this stage

  • ARIS
  • Process mapping
  • Stakeholder workshops
  • Requirements

Project context

HisnOwned

I define the product problem, intended users and scope for Hisn, connecting business need to an implementable product.

Marsad (NIMIC)Guided

I guide technical and platform constraints that shape ministry scope, integration boundaries and delivery feasibility.

GOSI PortalGuided

I guide how public-service needs translate into reusable portal capabilities and a feasible technical scope.

02 · Product & experience

Connect business intent to usable digital journeys, with UX/UI depth that carries through to implementation.

Decisions I shape or own

  1. How should the journey work for each user and role?
  2. Which design patterns maintain consistency across services?
  3. How do Arabic, RTL, accessibility and responsive behavior shape the experience?

What I deliver / define

  • User journeys
  • Information architecture
  • Wireframes / prototypes
  • Design-system guidance

Skills supporting this stage

  • Figma
  • Adobe XD
  • Design systems
  • HTML / CSS
  • Accessibility
  • RTL

Project context

HisnOwned

I design the user journeys, bilingual RTL experience and interface system for Hisn’s role-specific portals.

Marsad (NIMIC)Guided

I guide UX direction, shared UI patterns, Arabic / RTL behavior and consistency across public-service experiences.

GOSI PortalLed

I lead frontend and UX/UI direction, reusable components, responsive behavior and accessible service experiences.

03 · Solution architecture

Translate business, product and technical requirements into a solution teams can implement, with explicit decisions and trade-offs.

Decisions I shape or own

  1. Where are the solution boundaries, and which architecture style fits?
  2. What should we build, reuse or buy, given cost, risk and time?
  3. How do APIs, data, integrations and identity work together?
  4. Which trade-offs meet performance, security, availability and delivery constraints?

What I deliver / define

  • Solution views / C4
  • Architecture decisions (ADRs)
  • NFRs & trade-offs
  • Integration / API design
  • Architecture roadmap

Skills supporting this stage

  • Solution modeling
  • Modular architecture
  • API contracts
  • IAM / RBAC
  • Cloud & data design

Project context

HisnOwned

I own Hisn’s solution architecture across application boundaries, APIs, data, identity and multi-tenant isolation.

Marsad (NIMIC)Owned

I own the application-architecture remit: Angular/Nx modularization, SSR, API / BI integration and CMS modernization.

GOSI PortalLed

I lead application architecture and shared platform standards, aligning frontend patterns with enterprise integrations.

04 · Engineering

Turn architecture into practical engineering patterns, guide teams and contribute hands-on where it makes the greatest difference.

Decisions I shape or own

  1. Which patterns and shared components will teams use?
  2. Where do ownership boundaries sit across frontend, backend, integration and data?
  3. How do reviews, mentoring and technical standards protect quality?

What I deliver / define

  • Engineering standards
  • Reusable components
  • API contracts
  • Implementation guidance
  • Code reviews
  • Reference implementations
  • Reusable libraries

Skills supporting this stage

  • Angular
  • Nx
  • TypeScript
  • SSR
  • FastAPI
  • Node.js
  • PostgreSQL

Project context

HisnOwned

I build Hisn’s frontend, backend, integration and data layers, with reusable patterns connecting them.

Marsad (NIMIC)Led

I lead frontend engineering patterns, implementation reviews and technical quality within the program’s delivery teams.

GOSI PortalLed

I lead frontend patterns, reviews and mentoring so teams deliver consistent service experiences.

05 · Quality engineering

Define what ready means, and make quality measurable throughout the work, from technical design to user acceptance.

Decisions I shape or own

  1. What evidence must satisfy the Definition of Done?
  2. Which test layers and quality gates address the real delivery risks?
  3. What performance, accessibility and security thresholds must be met?

What I deliver / define

  • Quality expectations
  • Definition of Done
  • Performance budgets
  • Test / UAT criteria
  • Release-readiness evidence

Skills supporting this stage

  • Playwright
  • Lighthouse
  • Code reviews
  • Accessibility checks
  • Performance analysis

Project context

HisnOwned

I define Hisn’s quality approach: test priorities, acceptance criteria and technical readiness.

Marsad (NIMIC)Led

I lead technical-quality expectations for the frontend and integrations, aligning performance and accessibility with readiness.

GOSI PortalLed

I lead frontend-quality expectations around accessibility, performance, reusable components and technical reviews.

06 · Technical delivery

Turn product and architecture direction into coordinated execution, connecting priorities, teams, risks and release decisions.

Decisions I shape or own

  1. What is the next valuable delivery increment, and what can wait?
  2. Which dependencies, blockers and risks need action or escalation?
  3. How do team ownership, capacity, stakeholder alignment and technical readiness shape the plan?

What I deliver / define

  • Delivery roadmap
  • Prioritized backlog
  • RAID / dependency log
  • Ownership alignment
  • Release plan

Skills supporting this stage

  • Delivery planning
  • Team alignment
  • Architecture reviews
  • Stakeholder communication

Project context

HisnOwned

I own Hisn’s product priorities and delivery increments, connecting architecture, engineering and release planning.

Marsad (NIMIC)Led

I lead technical coordination: priorities, dependencies, blockers, engineering quality and stakeholder alignment.

GOSI PortalLed

I lead technical alignment across frontend work, shared capabilities, dependencies and delivery quality.

07 · Platform, DevOps & release

Govern how software moves from source code into production, with specialist teams and explicit readiness, cutover and rollback decisions.

Decisions I shape or own

  1. Which environment and deployment approach fit the platform?
  2. How will configuration, secrets and release risk be controlled?
  3. What must be validated before go-live, and how will we roll back?

What I deliver / define

  • Environment strategy
  • Pipeline expectations
  • Deployment / cutover plan
  • Rollback plan
  • Operational handover

Skills supporting this stage

  • GitHub Actions
  • Docker
  • Kubernetes
  • OpenShift
  • Helm
  • Terraform
  • AWS

Project context

HisnOwned

I own Hisn’s delivery approach and define deployment, configuration and recovery needs for the product.

Marsad (NIMIC)Guided

I guide technical release readiness and cutover dependencies, while platform and change teams own pipelines and approvals.

GOSI PortalGuided

I guide technical release readiness and cross-team dependencies within the program’s change and approval processes.

08 · Operate & improve

Use operational evidence and user feedback to improve the platform, strengthen engineering capability and inform the next priorities.

Decisions I shape or own

  1. Which signals reveal service health and user friction?
  2. What should we fix now, and what belongs in the improvement backlog?
  3. How do incidents, feedback and technical debt change the roadmap?

What I deliver / define

  • Observability expectations
  • Service / product KPIs
  • Improvement backlog
  • Technical-debt priorities
  • Operational insight

Skills supporting this stage

  • Sentry
  • Analytics
  • Logging
  • Performance analysis
  • Power BI / SSRS

Project context

HisnOwned

I own Hisn’s improvement backlog: product feedback, operational signals and technical debt become the next priorities.

Marsad (NIMIC)Led

I lead technical improvement priorities from platform performance, BI insight and delivery evidence within my architecture remit.

GOSI PortalLed

I lead continuous improvement for portal quality through performance findings, accessibility evidence and reusable engineering patterns.

02 / EXPERIENCE BEHIND THE PRACTICE

The same lifecycle.
Different kinds of ownership.

INDEPENDENT PRODUCT · END-TO-END OWNERSHIP

Hisn

An Arabic-native DLP and AI compliance platform that I designed, architected and built end to end. It connects product design, frontend, backend, data and multi-tenant SaaS delivery in one product.

Product & UXArchitectureFrontend & backendData & security
Explore Hisn in selected work
GOVERNMENT PROGRAMS · LEADERSHIP AT SCALE

Marsad, Tarmeez & GOSI

Architecture, technical leadership, frontend engineering and UX guidance within larger delivery teams. My contribution is grounded in the remit of each program, with specialist teams owning their respective disciplines.

ArchitectureTechnical leadershipUX guidanceDelivery governance
Explore the government programs

ARCHITECTURE · DELIVERY · ENGINEERING LEADERSHIP

A wider view. A practical foundation.

Business outcomes, user experience and engineering decisions connected through delivery.

Discuss an opportunity

Back to the full portfolio