OUR APPROACH

DESIGN THINKING

Design thinking is a human-centered approach to innovation—anchored in understanding customer's needs, rapid prototyping, and generating creative ideas—that will transform the way you develop products, services, processes, and organizations.
Design Thinking encourages organizations to focus on the people they are creating for, which leads to better products, services, and internal processes - best suited for "thinking outside the box"; is most useful to tackle problems that are ill-defined or unknown.

We use the 5 phase Design Thinking approach outlined by The Hasso Plattner Institute of Design at Stanford

1. Empathize - Conduct research on your Users' needs

2. Define - Analyze observations from the research - synthesize into problem statements

3. Ideate Think outside the box to come up with innovative solutions for the problem statement

4. Prototype - Build an inexpensive, scaled-down versions of the product

5. Test - Evaluate the prototype; learn; iterate.

Outputs from Design Thinking Workshops include but not limited to

1. Point of View (Problem Statement)

2. Affinity Diagrams

3. Customer Journey Maps

4. Empathy Maps

5. Stakeholder Maps

Customer Centricity

Customer-Centricity is an organizational mindset that focuses on creating positive experiences for the customer through the full set of products and services that the enterprise offers; places customers, rather than product or sales, at the center of the business.

Customer-Centricity will help you realign your performance metrics, product development, customer relationship management and organization to make sure you focus directly on the needs of your most valuable customers and increase profits for the long term.

ENTERPRISE ARCHITECTURE FRAMEWORK

Enterprise Architecture (EA) is a discipline for proactively and holistically leading enterprise responses to disruptive forces by identifying and analyzing the execution of change toward desired business vision and outcomes.


The four building blocks of EA are:

1. Business Architecture - A blueprint of the enterprise that provides a common understanding of the organization; connects business strategy and IT strategy to project execution.

2. Data Architecture - A formal approach (Data Governance) to creating and managing the flow of data and how it is processed across an organizations IT systems and applications.

3. Application Architecture - Interaction between application packages, databases, and middleware systems- managing how multiple systems work together.

4. Technology Architecture - Defines the infrastructure and security considerations for the enterprise.

The purpose of EA is to create a map of IT assets, business processes and a set of governing principles that drive an ongoing discussion about business strategy and how it can be expressed through IT.

Solution Architecture delivers the prescribed value enablement and capability improvement across the Business Architecture.

An architecture framework provides principles and practices for creating and using the architecture description of a system. Using an EA framework you can
  • Align IT projects & investments to your company's drivers, goals, and objectives
  • Support communication between different stakeholders from business and IT
  • Operationalize innovations by taking IT Strategy and existing investments into account.
We use the The Open Group Architecture Framework (TOGAF), a proven Enterprise Architecture methodology and framework; supported by a set of documents that provide specific guidance about how to use and adapt it to support new trends. The framework is foundational to our Value Realization Workshops, and in turn the Business Architecture Transformation imperative.

Maturity Model

Understanding an organization's Business Capability Maturity Levels helps us provide structured recommendations on how to elevate the sales and customer experience functions. We categorize business capability maturity into five levels.

  • Level 1: Minimal - The capability doesn’t exist in the current organization or is practiced on an ad-hoc basis.
  • Level 2: Emerging - The capability exists to a small degree, but isn’t mature or developed.
  • Level 3: Practicing - The capability is somewhat mature and delivers consistent value.
  • Level 4: Optimized - The capability is mostly mature and continually improved.
  • Level 5: Leading - The capability sets the industry standard and delivers significant value.

INDUSTRY FRAMEWORKS

Industry Frameworks standardize how business processes are designed and delivered between the industry core capabilities and its consumers.

An industry framework includes business process definitions, common data model, data exchange interfaces, integration approaches, pre-integrated solution options in collaboration with partners, best practices, governance model, and alignment with accepted industry standards

Industry Frameworks accelerate development on the Salesforce Platform and form the basis of Industry Clouds from Salesforce.

1. Understand core business processes in your specific industry

2. Analyze common data models, data residency requirements, and common data interfaces specific to your industry

3. Develop an Integration Plan that complies with your industry requirements

4. Identify Salesforce Industry Clouds with Out-of-the-Box (OOTB) features that accelerate implementation of Salesforce

5. Align with your Enterprise Architecture Governance Model

Reference Architectures

The reference architecture helps communicate the vision and strategy of a solution to business executives and stakeholders. They bring together
1. Platform Capabilities (Data Sources, Integrations, Intelligence, Analytics)
2. Functional Capabilities (Business specific elements at the functional level - the "Customer Experience")
3. Mapping Platform Capabilities to Salesforce (specific Salesforce products handle each of the needs identified at the platform capability level.)

CLOUD NATIVE STRATEGIES

Cloud native is an approach to building and running applications that exploits the advantages of the cloud computing delivery model. Cloud native development incorporates the concepts of DevOps, continuous delivery, microservices, and containers.
  • Quickly build and deliver applications in response to customer needs
  • Optimizes application lifecycle management
  • Enables teams to focus on resilience
  • Cloud native architecture facilitates DevOps; enterprises can transform into lean, focused teams aligned to business priorities.

1. Mulesoft (or Client's preferred tools) for Orchestration

2. Heroku for App Rationalization (Microservices & Containers

3. Salesforce native DevOps Tools

4. Hyperscalers for horizontal scaling

Salesforce Hyperforce

A completely re-architected Salesforce Platform; horizontally scalable and deployed on public clouds; can become an organization's Single Source of Truth
✔Hyper-scale
✔Local Data Storage (Data Residency)
✔Built-in-Trust & Compliance
✔Backwards Compatible

Leveraging Hyperscalers

We can use our expertise in leveraging hyperscalers to start building your enterprise strategy around Hyperforce.