Design Odyssey

‘Design Odyssey’
Redesigning deal pricing system of Wipro

A Project submitted to
Department of Fashion Communication
NIFT-Bengaluru

In partial fulfillment of the degree of

Bachelor’s of Design in Fashion Communication

Guided By
Mr. KC Prashanth
Associate professor
Fashion communication department

Submitted by
Raunak Agarwal
BD/15/199

Department of Fashion Communication

2015 - 2019

National Institute of Fashion Technology, Bengaluru - 560102

 Design Odyssey

2.
Design Odyssey

3.
Design Odyssey

Sponsored by
Designit, Bangalore

Document printed at : Print Xpress

9/5 Richmond Road,
Bengaluru, Karnataka, 560102

This document ‘Design Odyssey’ is a graduation project report created during my internship at Designit, Bangalore under
the acadamic curriculum of National Institute of Fashion Technology, Bangalore. All the work that have been included in
this project document are copyright protected. All copyrights reserved with Designit, Wipro.

No part of this document may be reproduce, distributed, or transmitted in any form including photocopy, recording, or
other electronic or mechanical methods without prior permission of Designit, Wirpo.

Edited and Designed by - Raunak Agarwal

Project guide - Mr. KC Prashanth
Industry Mentor - Mr Shantanu Singh

All right reserved.

B.Des, Fashion Communication (2015 - 2019)
National Institute of Fashion Technology, Bengaluru

raunakagarwal14@gmail.com
+ 91 7979 88 3096
 Design Odyssey

Declaration
I Raunak Agarwal, hereby declare that the Project titled ‘Design odyssey’ is a record of original work undertaken by me for
the award of the degree of B.Des in Fashion Communication.

I have completed this study under the supervision of Mr. Prashanth KC, Associate professor & Centre Coordinator,
department of Fashion Communication, NIFT Bengaluru.

I also declare that this project thesis has not been submitted for the award of any degree, diploma, associateship, fellowship
or other title. I hereby confirm the originality of the work and that there is no plagiarism in any part of the dissertation.

Place: Bengaluru

Date: 21st May 2019

Signature of the candidate

Raunak Agarwal
BD/15/199
Design Odyssey

Certificate
This is to certify that the Graduation Project titled ‘Design Odyssey’ at Designit, Wipro is a record of work done by the
student, Raunak Agarwal BD/15/199 as a Regular student for the degree of B.Design Fashion Communication during
the period of 07 Jan 2019 to 10 May 2019, which represents as independent work and does not form the base for any
previous work.

PLACE: Bengaluru
DATE : 21st May 2019

Under the Guidance

Mr. Prashanth KC,

Associate professor,
Department Of Fashion Communication
National Institute of Fashion Technology
Bengaluru - 560102.

------------------------ ------------------------ ------------------------

(External Jury Member) (External Jury Member) (External Jury Member)

-------------------------
(External Jury Member)
 Design Odyssey

Acknowledgement
I would like to thank NIFT Bengaluru to provide me this opportunity that shall stay with me for lifetime. I would also like to
express my gratitude towards my college mentor, Mr. KC Prashanth and my industry mentor, Mr. Shantanu Singh for their
constant guidance and invaluable support. To the wonderful team of designit and amazing people I came across through
this internship.
Lastly, I would also like to thank my friends, colleagues and family for always being there to help me grow at every stage.

Raunak Agarwal,
Department of Fashion Communication
NIFT Bengaluru
Design Odyssey

Joining letter
 Design Odyssey

Relieving letter

16th May 2019

16th May 2019

PROJECT COMPLETION CERTIFICATE

PROJECT COMPLETION CERTIFICATE

This is to certify that Mr. Raunak Agarwal Trainee ID 40023471 student of “National Institute of Fashion Technology,
Bangalore” has completed the project entitled “‘Design Odyssey’ - Redesigning the deal pricing system of Wipro”
This is to
under thecertify that Mr.
guidance Raunak Agarwal
of “Shantanu Singh”Trainee ID 40023471
at Designit student
Bangalore from 7ofth “National Institute
January, 2019 ofthFashion
to 10 Technology,
May, 2019 for the
Bangalore”requirements
academic has completed thegraduation.
of his project entitled “‘Design Odyssey’ - Redesigning the deal pricing system of Wipro”
under the guidance of “Shantanu Singh” at Designit Bangalore from 7th January, 2019 to 10th May, 2019 for the
academic
We have requirements
observed thatofyourhis graduation.
work was excellent and we appreciate your sincere learning.
You have performed the project with energy and enthusiasm.
We have
This letterobserved
is issued that
basedyour
on work was excellent and we appreciate your sincere learning.
your request.
You have performed the project with energy and enthusiasm.
Thiswish
We letteryou
is issued
all the based on your
very best request.
in your career ahead!

We wish
Best you all the very best in your career ahead!
Regards,
For Wipro Limited
Best Regards,
For Wipro Limited

40023471

40023471

Sensitivity: Internal & Restricted

Sensitivity: Internal & Restricted

 Design Odyssey

10.
 Design Odyssey

We’re a
team of 500+
thinkers and
doers spread
across 18
studios.
11.
 Design Odyssey

12.
 Design Odyssey

Content
Joining Letter ........................................................................................ 12

Relieving Letter ........................................................................................ 13

About ........................................................................................ 14 - 21

Project biref ........................................................................................ 24 - 27

Design Process ........................................................................................ 28 - 29

Research ........................................................................................ 30 - 39

Ideation of Future Journey ........................................................................................ 40 - 49

Secondry Research ........................................................................................ 50 - 63

Style guide ........................................................................................ 64 - 79

Pre-Design workshops ........................................................................................ 80 - 101

Learning ........................................................................................ 102

Bibliography ........................................................................................ 103

13.
 Design Odyssey

About Wipro
Wipro Limited is an Indian multinational corporation that Its application services offerings include Oracle
provides information technology, consulting and business Application Services, SAP Application Services, Connect-
process services. It is headquartered in Bengaluru, ed Enterprise Services, Cloud Application Services, En-
Karnataka, India. terprise Architecture, Enterprise Security Solutions and
Testing Services.
Headed by chairman Azim Premji, son of the founder,
Mohamed Hasham Premji, Wipro Ltd started out in 1945
as Western India Products, a company that sold vegeta-
ble oil. The company later diversified into the manufacture
of soaps and other consumer products and ventured into
technology in 1985, selling locally-made computers.

The Company’s IT Services business provides a range of

IT and IT-enabled services. IT Products segment
provides a range of third-party IT products, which allows
it to offer IT system integration services. The Company
offers integrated business solutions that span across
enterprise applications and digital transformation to secu-
rity and testing.

Service offerings

- Data, Analytics & AI

- Applications
- Digital Operations and Platforms
- Consulting
- Cloud & Infrastructure Services
- Product Engineering

14.
 Design Odyssey

1945
Incorporation of Wipro

1982
Entry into IP products Business

1990
Entered into 3rd party R&D service and IT
service

2000
Listed in NYSE and
enters the BPO business

2015
Launched ‘Wipro Digital’. Key capabilities
acquired through Designit & Appirio

2017
Launched new Brand identity & rearticulat-
ed ‘Spirit of Wipro’ to underscore Wipro’s
commitment to transform & evoling client
expectations

2018 - 2019
Aquired Cooper design

15.
Design Odyssey

Designit

D esignit is an international strategic design firm

founded in Aarhus, Denmark, in 1991 by Anders Geert
Jensen and Mikal Hallstrup. Designit headquarters is
Wipro Digital, the digital unit of India’s third largest
software company Wipro, acquired Designit.

located in Copenhagen, Denmark, with 18 offices across
the globe. Designit offers integrated strategic design and
innovation services, including product design, service
design, and experience design, with an emphasis on
mobile and digital media. The company recently expand-
ed its services to include consulting in business design.
This enabled them to evolve its go-to-market digital
offerings. Designit’s capabilities in strategic design, user
experience and interaction design complements Wipro
Digital’s capabilities in technology, digital strategy, design
and digital architecture.

Designit’s employees work in cross-disciplinary teams,

involving clients and end-users in the design process.
Designit works in various sectors, including healthcare,
finance, IT, telecommunications, automotive and consum-
er goods.

Service offerings

- Business strategy and venture design

- Service and customer experience design
- Product and industrial design
- Digital design and technology
- Brand and graphic design
- Architecture and space design
 Design Odyssey

Workspace
Rich with open, beautifully lights-caped workspaces and diverse-
ly-textured dens and corners, the Pod is a creative’s dream.
There are quick “catchup” spots for small groups, a library with
“high chairs for tall minds,” and open seating areas where the
next big invention is just a neighbor away. In an environment
where innovation leads, there are no manager cabins, only spac-
es designed to foster the next great idea.

To
w
ar
ds
ai
rp
or
t
Studios around the globe Electronic
City flyover
e
enu
Av
ys
os
Inf
Aarhus Barcelona Bengaluru Berlin Copenhagen Lima
London Madrid Medellin Melbourne Munich New York
Oslo San Francisco Stockholm Sydney Tel Aviv Tokyo
e
Avenu
Wipro

Neela
dri Ro Wipro
ad
Junction

Designit,
d
in R

Bengaluru Wipro EC,

Tower 08
Ma

Tower 23, Wipro EC4

lya

Internal Rd, Shikaripalya,

ripa

Electronic City, Bengaluru,

ika

Karnataka 560100
Sh

17.
 Design Odyssey

Designit clients
Combining design and technology, designit help businesses change and grow. They solve complex problems for
companies across the world. Some of the noticible companies that designit worked with are listed below.

18.
Design Odyssey

19.
 Design Odyssey

Organisational structure

CEO
Abidali Neemuchwala

Digital Head MIT CSO

Rajan Kohli GK Prasanna Rishad Premji

VP digital CIO
Sudhir Kesavan Raja Ukil

MD IT transformation
Peyush Agarwal Sharada N.

Design director
Udhay Padman.

Design lead
Shantanu Singh
Project mentor

UX intern Lead UX Digital designer

Raunak Agarwal Ranjit Ravi Kinshuk Bose
 Design Odyssey

CFO COO CHRO

Jatin Dalal Bhanumurthy B.M. Saurabh Govil

Wipro
Designit

Digital designer Digital designer

Sabyasachi Jery M.
 Design Odyssey

IT industry
Information Technology (IT) industry has become one
of the fastest growing industries in India. According to
NASSCOM, India’s IT & ITeS industry grew to US$ 167
billion in 2017-18. Exports from the industry increased
to US$ 126 billion in FY18 while domestic revenues
(including hardware) advanced to US$ 41 billion.
Key players of IT in India like Wipro, Tata, Infosys has
contributed significantly to this achievment by providing
breadth of service offering, along with cost advantage
and highly skilled professionals. Surprisingly, revenue
from digital segment is expected to comprise 38 per
cent of the forecasted US$ 350 billion industry revenue
by 2025.
Being the top face of IT, organization like Wipro have
establish its strong credentials by providing a broader
spectrum of services from IT solutions, product imple-
mentation & consulting services to business include
software development and consumer care & health
science. The major revenues come from products and
services (28%), closely followed by financial services
(23%).
But, since each organization is unique in how it func-
tions, it is a great challenge when it comes to sustain-
ability in the growing market. As the business grows,
your strategy needs to evolve too.
For instance, Wipro is building computing systems
designed to mimic human decision-making abilities,
where machines can understand and react to what
human beings say to them.
Other centred around simplification which is primarily
around operational simplification of processes in
everything wipro do in terms of their customers, em-
ployees, and partners through the use of cutting-edge
technologies like automation, robotics, artificial intelli-
gence.

Project
background
Project Quantum is started to transform the process ‘One Wipro’. The vision of this program is also to serve
and functionality within Wipro in order to make it more as a ‘showcase of the future’ for Wipro’s clients and
sustainable and agile. A new process that will bring bring empowerment with accountability.
significant difference in the functioning by Wipro by
empowering its team to deliver growing value to its In order to accomplish the project of such scale, Quan-
client. tum is divided into various tracks. These tracks are
running in parallel to accomplish the work within short
Oganization like Wipro envolves large-scale corpo- period of time. The tracks represents various business-
rate-controlled financial or business activities. Project processes in Wipro.
Quantum is one of the Wipro’s internal project that
aims at transforming and reimagining the entire pro-
cess and system landscape within Wipro. Quantum
aspires to deliver a unified view of Wipro, across var-
ious organisational dimensions of people, processes
and systems, and install agility as a core principle of

22.
 Design Odyssey

Area of
engagement

23.
 Design Odyssey

Project
brief
The aim of my project was to Redesign the deal pric- The expected project deliverables included documen-
ing system of wipro which constitute an integral part tation and evaluation of the insights gathered in order
of lead to order* track. The project required an indepth to present strategic approach and opportunity areas
understanding of Wipro’s business model and its func- followed by proposing and updating project style guide;
tionality. exploring and creating visual design for web and mobile
version for various key user across deal pricing cycle
Various activities like understanding the current journey, keeping the key findings in consideration.
business requirement, understanding user and stake-
holders, interviewing, shadowing, and desktop research
followed by ideating, conceptualizing, proposing strat-
egies and user testing helped in finalising the project.

Objective
To redesign the Wipro deal pricing system in order to support
its existing and future business models. Enable Wipro and it’s
employees achieve their business goals through a more
human-centric approach.

Goals
- Reduce the manual effort and time required to configure and complete the
deal pricing and estimation for Wipro.
- Design a process that enables collaboration, flexibility, and agility for
different actors involved in the system.
- Use the upcoming technologies to increase learnability, predictability, and
efficiency of the system.
- Create a platform that allows future scenarios and scalability for business
in Wipro

24.
 Design Odyssey

The project required

· Understanding the proposed process

· Requirement gathering and validation with business users
· Creating IA and user flows
· Creating design concept and detailed interaction designs
· Maintaining and updating the Quantum Design Library
· Creating Interactive prototypes
· Conducting User testing and validation sessions
· Design governance and hand-over

25.
 Design Odyssey

)
)

)
an )

Feb

Feb

Feb
Jan

Jan

Feb
11 J
Project

- 18

- 25

- 08

- 15

- 22
-1
an -

Jan
Jan

Jan

Feb

Feb

Feb
timeline

(7J

( 28
( 14

( 21

( 04

( 11

( 18
W1 W2 W3 W4 W5 W6 W7 W

My entire graduation project tenure of 18 weeks

was distributed in various phases.

- Onboarding • Project Onboarding and knowledge transfer

- Research • Understanding the vision and research report study

- Interview & painpoints

- Ideation & prototypes
- Final design
- Presentation & feedback

Secondary & primary research

• Current process study

• Understanding current user journey

• Current system study, heuristic analysis,

• and feature documentation

• Competitor Analysis & tool study

• Documentation and validation

Stakeholders & User int

• Understand the role

• Prepare questionna
• Conduct stakehold

• Synthesise the data

• Create persona and

• Validation workshop
• Document and eva

26.
 Design Odyssey

ay )
ar )

ar )

ar )

ay )
)

pr )

pr )

pr )

pr )
r)

ar )
F eb

F eb

F eb

Ma

15 M

22 M

29 M

10 M
03 M
05 A

12 A

19 A

26 A
8M
- 08

- 15

- 22

-1

ar -

r-

r-

r-

y-
-
F eb
F eb

F eb

F eb

Apr

Apr

Apr

Apr

Apr
Ma

Ma

Ma

Ma
(4M
( 25

( 01

( 08

( 15

( 22
( 04

( 11

( 18

( 11

( 18

( 25

( 29

( 06
W5 W6 W7 W8 W9 W10 W11 W12 W13 W14 W15 W16 W17 W18

er
port study

Design Ideation

• Create detailed Information architecture (to be

plugged in WiproOne IA)

esearch • Adopting business tech innovations in new

system.

tudy
• Create design explorations and prelim concepts

rrent user journey

• Create task-flows and scenarios

udy, heuristic analysis,

• Validation & Documentation
mentation

sis & tool study

nd validation

Detail Design - Wipro one

• Wireframes + Visual Designs

• Interaction design documentation

• Clickthrough prototype

• Design walkthrough

• Final Consolidation of the project & presentation

Final presentation


Stakeholders & User interviews to collect pain points & feedback

Presentation with Designit team + feedback

• Understand the role & responsibility of the actors involved in current journey
Final Presentation with Quantum Team
• Prepare questionnaire and schedule discussions with users and stakeholder

• Conduct stakeholder interviews and contextual inquiries with users

• Synthesise the data from interviews to draw pain-points and opportunity areas

• Create persona and future user journeys for involved actors

• Validation workshop with stakeholders

• Document and evaluate the feedback

27.
 Design Odyssey

Design process
1. Inspiration

This is the phase of empathy, where the designer gets immersed in the user’s lives, and understand their needs in
great depth. The designer makes sense of all the learning, and identifies opportunities for design. Inspiration is the
first step towards creation of a product or service. Observing how things and people work in the real world is very
helpful for drawing inspiration.

Activity

This phase was a user-focused approach, and intended to find answers to the following questions.

1. What is a deal pricing system in wipro?

2. Who are the key stakeholders and users?
3. What are their current painpoints and challenges in using DPS?
4. How can this be solved?

Research method

Interview

User interviews helped me uncover what’s important to the

users and what they want from our design. This helped to
create user stories and determine content and functional
requirements before we start with our design.

An open ended question session helped in understand the

entire process and challenges users faces on day to day
activity.

Shadowing

This method was solely based on observation, wherein I

observes how the user would behave towards a product/ ser-
vice within their natural working environment. I was expected
not to interfere with the user/participant, as this might
change the way the participant would behave in a given
situation. This method was considered in order to observe
how a sales person would behave during different phases of
the day.`

28.
 Design Odyssey

2. Ideation
This stage required restrain from limiting ourself and approach ideation with an open mind. Divergent
thinking and more ideas are what lead to disruptive solutions and are beneficial in the long-run. This is
the phase where the designer ideates for solutions, and prototypes possible solutions.

3. Implementation
It is the key to the creation of the final product or service. In this space, prototyping is extremely import-
ant. Testing within a small and well chosen sample set of users can help create a revolutionary product.
The
designer makes the solution alive, evaluates it based on the user needs, and then eventually brings it to
market.

Research tools

Primary research
Understanding current Journey - Deal pricing system
Personal interview with stakeholders and key user

Secondary research
Competitor analysis - Tool study
Market trends
Keyboardability

29.
 Design Odyssey

Identifying
key users

Sales

Sales reps are responsible for maintaining existing client relationships. They are the main
point of contact for the company’s clients, and are expected to retain their business and
build a strong business relationship.

Presales

Presales are the people who preparation/management proposal based on customers

requirements. The presales professional understands what the customer needs, devel-
ops an initial view of the solution, then tailors the product or service of his company to
meet what the customer needs, explains (or helps sell) this solution to the customer,
helps close the deal or sale and often stays on to ensure that the delivery team or product
specialists that follow him provide the intended solution.

Delivery Manager

Delivery Manager oversees a number of key functions within the IT department that
enable the delivery of a high quality service to client, and to ensure Service Support and
Service Delivery processes are in place to meet business needs. This position is a stake-
holder facing role, and requires that you establish and manage expectations within the
business and drive the IT team to achieve those expectations to a high standard.

BFM (Business finance manager)

Business finance manager key role is the formulation of budget and cost estimates,
presenting and defending budget estimates, review and evaluation of budget requests,
control and reporting of obligations and expenditures throughout cycles of the deal.

Legal head

Head of Legal is tasked with the implementation of key legal processes that relate to
legal drafting, negotiations, and commercial settlement agreements. They takes a lead-
ing interest in the management of the business resources and budget allocation for the
business’s legal activity.

30.
 Design Odyssey

Understanding
Deal pricing in Wipro

In the lead to order lifecycle, create phase is all about demand generation wherein the lead is converted into an
opportunity. Once the opportunity is created and accepted by sales, it enters into the second phase ie. qualify stage.
The qualification is based on the ground whether the Wipro can serve the opportunity. Various parameters helps in
identifying if the Wipro can pursue that opportunity.

Deal lifecycle

Sales person drives an opportunity and recieve a RFP (Request for proposal) by client. He will identify the presales
person from the vertical of that particular account ie. Deal owners. For a given account, a deal owner breaks down
the scope of work into logical chunks of work ie. work stream or modules. The breakdown is based on various service
lines, vertical, practice or sub practices. These workstream or module will be futher owned by the respective module
owners and sub workstream owners. The deal owner provides them with the RFP and expect them to come up with
the solution. Each module owner will start analysing the RFP and works on corresponding solution pieces.

Module owner enters RLS, passthrough, and IP details for corresponding modules . This is followed by finance person
from deal team selecting deal parameters, modifying parameters like rate inflation, billing hours etc and thus calculat-
ing the deal and generating summary details.

Stages

- Creation of new deal

- Import opportunity details from trace
- Assign team members
- Create modules and assign module owner
- Enter RLS details by module owners
- Selection of deal parameters by finance
- Calculation of Deal

31.
 Design Odyssey
Current journey
(Opportunity Owner)
Creation of deal
Sales
An sales guy can create a deal
against an opportunity by filling
in the corresponding opportu-
nity number.
(Deal Owner)
Pre-sales
Assign deal team
A team is formed by deal
owner consisting of people
from various divisions
(Module Owner)
Enter RLS for
Pre-sales
corresponding module
Each module owner is provide
with RLS template from clients
which they need to submit
within provided timeline.
(Deal team)
Select deal parameter
BFM
Parameters like assets, pay-
ment, discount, country, billing
currency are set here by the
BFM guys from the deal team.
32.
Importing opportunity
details from trace
The existing opp. will prefill
most of the parameters at deal
creation stage like opp ID, Opp
owner, SUB, vertical etc.
Create phase & module
within the deal
The deal owner breaks the
SOW into multiple phase &
modules and provide a timeline
Download, fill, upload
RLS template
Various activity including down-
loading, filling and uploading
of RLS, passthroughs and IP
details
Add parameters like rate
inflation, billing hours etc
The value of these parameters
are added by finance people
and various versions of the deal
are generated.
 Design Odyssey

Enter additional details Sending proposal

Assign deal owner
for the deal to client

Additional details like deal Opp. owner assigns a deal

name, RFP, currency, date owner who is generally a
etc is filled by the opp. owner presale guy of the correspond-
before preceding forward. ing DU.

Enter details and Review at deal

assign module owner level

Provides additional details for

module and assign owners to
each modules.

Calculate
RLS and module

A module owner can calcute

his module level details and
modify any parameters.

Calculate
deal button Summary details

Finally the total value of deal The summary button brings

and corresponding details are the entire summary of the deal
calculated and a summary is and module and is ready to be
generated. shared with the client.

33.
 Design Odyssey

User interview & tool

walkthrough
Involving users in the design process is a crucial step to meeting both your users’ needs and your organization’s goals. A
key idea of the interiew was to get a thorough understanding of both user and business goals to gain insight on what your
users want, what’s working well on your current process and where you need to make improvements.

Approch
In-Depth interview and walkthough of the current confluence tool in order to map out key functionality,
challenges, and scope of improvements. The questions were mostly open ended and framed in such a way that it can
bring the most essential insights about the entire DPS.

34.
 Design Odyssey

Current system
painponts
The walkthough of current DPS helped me understand the process in detail. Various experience callenges and painpoint
were clealy visibile to me. Some of these challenges are :-

• The current system is extremly slow and the user needs to stay on wifi for all the activity.
• For larger deal, it is hard to manage timeline and efforts put by various employee, thus
the accountability is lost.
• The conversations were happening mostly through mail or offline. Thus, these informa-
tion were going unregistered.
• There is no common platform like teams or slack for team to colloborate and share.
• For complex deal with multiple level of modules and timelines, there was no single
source of visibility and information
• No prediction or assitance were provided to the users throughout the deal cycle.

35.
 Design Odyssey

36.
 Design Odyssey

Key
interventions
The key finding that came out of the research revolves around solving the basis problems faced by user across the deal
pricing system. The basic features like date and timeline managemnet in order to keep a track of the activities and dead-
lines were missing. Other issues like uploading of RLS is tricky and complicated. No standard guildlines were governing
the tool and pricing science seems not transparent.

The idea was to bring a system that is transparent, flexible and intuitive. A system that eliminate the
redundency in process and will bring better collaboration amongst teams.

Streamlined process Effective collaboration

Track past, present & upcoming proposal status Real-time collaboration between response creation
& review team. Clear visibility & ownership of tasks
& dependencies.

Proposal repository integration Unified RFP response

Historic data analysis to make recommendations / Single point for proposal response creation by
suggestions multiple members. Flexibility to incorporate new
requirements to the template without going out of
the system

Deal Assessment parameters

Standardised but customisable deal assessment
parameters to assess the deal of every size S,M,L

37.
 Design Odyssey
(Opportunity Owner)
Future journey
Sales
(Deal Owner)
Pre-sales
Assign deal team
A team is formed by deal
owner consisting of people
from various divisions
(Module Owner)
Assign module team
and add module-phase
Pre-sales
details
Module team is formed by
Module owner and module
level phases are created.
(Deal team)
Select deal parameter
BFM
Parameters like assets, pay-
ment, discount, country, billing
currency are set here by the
BFM guys from the deal team.
38.
Design Odyssey | Research
Assigning deal owner
at opp. stage
Opp. owner assigns a deal
owner who is generally a
presale guy of the
corresponding DU.
Create phase &
module within the deal
The deal owner breaks the
SOW into multiple phase &
modules and provide a timeline
Draft tech solution of
corresponding module
An author from module team
draft response to strawan doc.
Add parameters like rate
inflation, billing hours etc
The value of these parameters
are added by finance people
and various versions of the deal
are generated.
Creation of deal deal
An sales guy can create a deal
against an opportunity by filling
in the corresponding opportu-
nity number.
Enter details and
assign module owner
Provides additional details for
module and assign owners to
each modules.
Fill RLS template in
commercial
Various activity including down-
loading, filling and uploading
of RLS, passthroughs and IP
details
Calculate
deal button
Finally the total value of deal
and corresponding details are
calculated and a summary is
generated.

Importing opportunity
details from trace
The existing opp. will prefill
most of the parameters at
deal creation stage like opp
ID, Opp owner, SUB, vertical
etc.
Identify phase & setup
pursuit calendar
Deal owner now create phase
and setup calendar by creating
various actions
Share commercial
report in Tech Sol.
The summary of commercial is
shared via tech solution action.
Enter additional details
for the deal
Additional details like deal
name, RFP, currency, date
etc is filled by the opp. owner
before preceding forward.
Create strawman
document and sections
A strawman list is generated
consisting of multiple doc
and sectioning.
Consolidate tech
solution for approval
Final consolidation of tech sol
document is done to share
with approver
Design Odyssey
Sending proposal
to client
Once the doc is approved, it
is ready to be shared with the
client.
Technical review at
deal level
Another approver at deal
level cross-check the final
consolidated incoming doc.
Technical review at
module level
An approver at module level
check over the doc and
approves or rejets it.
39.
 Design Odyssey

40.
 Design Odyssey

Ideation of
future journey

• Ideation workshops with business owners

• Defining key users
• Building scenario & use cases
• Defining Future process journey

41.
 Design Odyssey

Process ideation
Workshop 01
The keyhigh light of the workshop revolves around
detailing of the current process into a future state jour-
ney. The discussion goes around the idea of filling the
gap that emerges out of the interviews and providing a
viable solution keep the guiding principle in mind. The
idea to introduce a pursuit calendar to track all deal
related activities, manage and masure teams efforts &
contribution. Timely planning for project execution was
coined.
Along with the calendar, digital assistance through AI
wish will push contents from the previous deal repos-
itory was also introduced, which was later called as
KM push. The creation of multiple module and phases
needed to be captured dynamically which will provide
instant idea about the timeline. We went on to detail
out the journey with the constant bussiness & process
insight from the EY.

Detail the current process into detailed future journey

- Deal module planner

- Pursuit calendar
- Tech solution
- KM Push
- Digital assistance

42.
 Design Odyssey

New
deal lifecycle
In the lead to order lifecycle, create phase is all about
demand generation wherein the lead is converted into
an opportunity. Once the opportunity is created and
accepted by sales, it enters into the second phase ie.
qualify stage.
The qualification is based on the ground whether the
Wipro can serve the opportunity. Various parameters
helps in identifying if the Wipro can pursue that
opportunity. Business solution panel are the opportunity
line and is comprised of service lines, IP, soltuions and
alliances that gonna work together.
3. Digital RLS & deal pricing
Catalyst - It is a knowledge management document.
This content should be pushed to the respective
worksteam content owners. Similar relevant proposal
from past, relevent credentials, who have worked for
similar SOW. These are essential for the author who is
drafting this content for similar module and this sourc-
ing and pushing the content, which will assure a better
response for the client. Digital assistant based on AI
works in background in order to articulate the right
content for specific deals.

1. Deal configuration 3. Technical solution

Sales person drives an opportunity and recieve a RFP
(Request for proposal) by client. He will identify the
presales person from the vertical of that particular
account ie. Deal owners. For a given account, a deal
owner breaks down the scope of work into logical
chunks of work ie. work stream or modules.
The breakdown is based on various service lines,
vertical, practice or sub practices. These workstream or
module will be futher owned by the respective module
owners and sub workstream owners. The deal owner
provides them with the RFP and expect them to come
up with the solution. Each module owner will start an-
alysing the RFP and works on corresponding solution
pieces.
A tech solution consist of strawman list of documents
that is needed to create a proposal. These document
can be requested at any level by deal team, deal owner
or module owner. The deal owner will create the doc-
uments, sections and sub-sections and tag it against
a module. The author from the corresponding module
team will draft the content of the document while the
approver check over the final content before sending it
for final proposal.

2. Deal collaboration

Deal Team & module team (Delivery assurance team)

- The deal team and module team works in a collab-
orative platform to carry out their funtions effectively.
The team needs to collaborate on regular basis for deal
solutioning related activities. A collaborative section
along with digital assistance and team formation make
the process really effective. The deal owner can get a
overall view of the module and phase timeline through
a deal planner.

43.
 Design Odyssey

User scenario
Proposal planning &
Response Team

DEAL TIMELINE
Governance
Proposal Quote Submit Contract Orderbook

MEDIUM DEAL 1
Every type of deal (S,M,L) has standard steps
Filters

Week 1 Week 2 Week 3 Week 4

to complete the response, which need to be
Tasks 1 completed within an assigned timeline (like 2
- Entry 1
- Entry 2
- Entry 3 weeks for small deals, 3 weeks for large deals)

Task 2
- Entry 1
Every response team member can see at
which stage they need to get involved, what
- Entry 2
- Entry 3

Task 3
they need to do & status of completion
- Entry 1
- Entry 2
- Entry 3

Proposal template
PROPOSAL DETAILS
Response team start putting together their spe-
Client Name Opportunity ID cific scope in the PRE DEFINED PROPOSAL
Lead Creation
Stage TEMPLATE.
Project Name Business Requirements Generic content gets auto populated in online
Lead Opportunity Proposal Contract Order Book
response template from the details filled in
LEAD CREATION STAGE. (like, client name,
Wipro Unified
Sales Platform
Opportunity Details Leads to Review

Client Name

project name, background, business require-

20/08/17

Scope 1 Scope 2
21/08/17
Project Name
Anuradha

ment)
22/08/17
Recent
Business Requirement
24/08/17

Background
29/08/17

02/09/17
This ensures all required fields are filled & the
Details Details
response is in a uniform format

Collaboration on response
PROPOSAL DETAILS
creation
Client Name Opportunity ID

Team members can add supporting

Project Name Business Req.
documents if required like POC, POVs,
additional pitch slides etc.
Scope 1 Scope 1

Details Details

44.
 Design Odyssey

Proposal iteration
OPPORTUNITY

Based on the structure of the

opportunity, the system gives prompts of similar
proposals built in the past.

Similar Proposals

As the proposal is built, various team members

can chat & iterate on the response within the
portal itself.

Leadership Team
For complex proposals, DU/BU heads are also
part of response creation & can comment on
the feasibility of solution at much earlier stage

RFP DOCUMENT COMMENTS SCORE CARD

7.5

45.
 Design Odyssey

Sitemap

Mapping entire journey

Role specific distribution

46.
Design Odyssey

47.
 Design Odyssey

Role specific
distribution -
Deal owner

48.
 Design Odyssey

Role specific
distribution -
Module owner

49.
 Design Odyssey

50.
 Design Odyssey

Secondary research

• Tool study
• Management tools
• Keyboard accessability

51.
 Design Odyssey

Management tools
CRM
Customer-relationship management (CRM) is an
approach to manage a company’s interaction with
current and potential customers. It uses data analysis
about customers’ history with a company to improve
business relationships with customers, specifically
focusing on customer retention and ultimately driving
sales growth. CRM system, a tool that is used for con-
tact management, sales management, productivity, and
more. The goal of a CRM system is simple: Improve
business relationships.
How do different business functions benefit
from using CRM?
1. Sales teams can use CRM to understand their sales
pipeline better.
2. Marketing teams can use CRM to make forecasting
simpler and more accurate.
3. Customer service teams can effectively track conver-
sations across channels.
4. Supply-chain, procurement and partner management
teams can manage relationships better.

What does CRM software do?

HubSpot CRM
CRM software records customer contact information Salesforce Essentials
such as email, telephone, website social media profile, FreshsalesCRM
and more. It can also automatically pull in other informa- Pipedrive
tion, such as recent news about the company’s activity, Zoho CRM
and it can store details such as a client’s personal
preferences on communications

ERP

ERP is a system for improving the efficiency of busi-

ness processes. Like CRM, ERP allows for the rap-
id sharing of standardised information throughout all
departments. Employees all enter information into
the ERP system, creating a real-time, enterprise-wide
snapshot. Problems in any area will automatically
create alerts in other affected areas. This allows
departments to begin planning for issues before they
become a problem in that department.

Microsoft Dynamic Difference between ERP & CRM

SAP
Salesforce ERP and CRM systems use different approaches to
Oracle JD Edwards increase profitability. ERP focuses on reducing over-
heads and cutting costs. By making business processes
more efficient, ERP reduces the amount of capital spent
on those processes. CRM works to increase profits by
producing greater sales volume.

52.
 Design Odyssey

Project management Softwares

Confluence

Confluence is a digital platform for delivery. A role based consolidated platform, bringing order to billing applications under
one umbrella. Currently Wipro works with microsoft dynamic for its business and client management. The management
tool works on web based model at Wipro. Various stakeholders and business leaders access the platform for regular
pricing activity like deal & team creation, module creation, tracking deal status, SOW creation and sending proposal to
clients. Various features like automation and digitalization of data entry and maintenance had contributed to the system
for years and let the user had a seamless interaction.

Microsoft dynamics NAV

Microsoft Dynamics is a line of enterprise resource planning (ERP) and customer relationship management (CRM)
software applications. Microsoft Dynamics forms part of “Microsoft Business Solutions”. Dynamics can be used with other
Microsoft programs and services, such as SharePoint, Yammer, Office 365, Azure and Outlook. Microsoft Dynamics NAV
is a product which is part of the Microsoft Dynamics family, and intended to assist with finance, manufacturing, customer
relationship management, supply chains, analytics and electronic commerce for small and medium-sized companies and
local subsidiaries of large international groups.

SAP & SAP JAM

SAP ERP is an enterprise resource planning software developed by the German company SAP SE. SAP ERP incorpo-
rates the key business functions of an organization. Business Processes included in SAP ERP are Operations (Sales
& Distribution, Materials Management, Production Planning, Logistics Execution, and Quality Management), Financials
(Financial Accounting, Management Accounting, Financial Supply Chain Management), Human Capital Management
(Training, Payroll, e-Recruiting) and Corporate Services (Travel Management, Environment, Health and Safety, and Re-
al-Estate Management).
SAP Jam is a cloud-based enterprise social networking suite and collaboration app that helps users connect with employ-
ees, partners, and customers. SAP Jam can be utilized to protect company data by collaborating over a secure network.

53.
 Design Odyssey

Tools analysis
Zoho CRM

AI Integration Performance timeline

• Prediction Score • Anomalies

Win probability indication for each deal by Spot the irregularities in the deal and alerts the
analyzing and comparing these activities right stakeholder.
to usual win pattern.
• Prediction Future
• Prediction Filter Helps to predicts a future trend from past
Advanced Filters to sort out records with performance and data
similar patterns, scores, or activity.

54.
 Design Odyssey

SalesSeek

Visual sales funnel

• Highly visual and interactive UI • Drag & drop functionality

Get complete visibility over Sales pipeline at a Grant access to various department by simple
single glance and gamified interaction.

55.
 Design Odyssey

Tools analysis
Teamgantt

• Resource management Drag & Drop Simplicity

• Time tracking
• Multiple projects in one Gantt Change start and end dates, reorder tasks,
• Chart Dependencies between tasks and adjust your timelines in a single click
• Collaborate and share with team

See every project update and document on a single page and quickly share them with both internal and
external stakeholders

56.
 Design Odyssey

Ganttpro

Drag & Drop Simplicity Manage team and track progress

Change start and end dates, reorder tasks, and Comment on tasks and attach files to them - there is no
adjust your timelines in a single click. need to switch between different tools as all important
information is stored in GanttPRO

57.
 Design Odyssey

Keyboard accessability

K eyboard accessibility is one of the most import-

ant aspects of web accessibility. Many users with
motor disabilities rely on a keyboard. Blind users also
buttons, fields for inputting text, etc. A sighted keyboard
user must be provided with a visual indicator of the el-
ement that currently has keyboard focus. A basic focus
typically use a keyboard for navigation. In addition to indicator is provided automatically by the web browser
traditional keyboards, some users may use modified and is typically shown as a border (called an outline)
keyboards or other hardware that mimics the function- around the focused element.
ality of a keyboard.
A keyboard user typically uses the Tab key to navigate
through interactive elements on a web page—links,

Drag & Drop Simplicity

• The default keyboard navigation order must be logical and intuitive.

• The visual flow of the page: left to right, top to bottom - header first, then main navigation, then page
navigation (if present), and finally the footer.
• The Tab key can be used to navigate through links and form controls, Enter (and sometimes Spacebar) selects an
element, and the arrow keys are sometimes used for other navigation.

Youtube casestudy

Every part of the youtube player is keyboard navigable. The volume controls slide out when you tab focus away from the
mute icon, in contrast to sliding out when hovering over the mute icon.

58.
 Design Odyssey

Every browser had its own native implementation of :focus, although each varied in style. YouTube hadn’t defined any
custom :focus styles, instead relying on the browser’s native styling to visually indicate which elements I was tabbing
through.

Chrome focus styling —

the famous blue outline.

Firefox focus styling —

a dotted outline.

Safari focus styling —

similar to Chrome but the blue halo
is not as thick.

Opera focus styling is identical to

Chrome - They are both built on the
Blink browser engine.

IE11 underlines the link with a

dotted line.

59.
 Design Odyssey

Key takeaways

AI Integration Collaboration

AI detects patterns and Efficiently share any infor-

predicts behaiors, and make mation over a collaborative
smart remmendations about platform enhances customer
every interaction satisfaction

60.
 Design Odyssey

Accessibility Creative UI interactions

Designing the system which Enhance user engagement with
will cater to diverse audi- a product by creating emersive
ence - ERP patterns, acces- interface which is fun to interact
sibility guidelines, discovery. with and easy to handle.

61.
 Design Odyssey

62.
 Design Odyssey

Visual design &

explorations

• Updating quantum styleguide

• Pre-design workshops
• Desing exploration
• Versions and iterations

63.
 Design Odyssey

Quantum styleguide

Brand manifesto & guidelines

Project Quantum is aimed to define a digital first The elements that are part of the brand toolkit: Brand-
guideline with an emphasis on scalability while keeping mark, Colour, Typeface, Photography, Infographics,
intact the elements and synergy of the parent brand, Grids, the Wipro disc and iconography.
Wipro.

We used a process of VISEQ (Visual Equity) to identify

all the elements from the Wipro brand toolkit which are
carried forward and evolve the elements which cannot
be scaled for a digital interface.
Colour Typeface

Brandmark Photography

Infographics Iconography

Viusal Equity
Wipro Disc Grid &
Layout

VISEQ or Visual Equity is a system of evaluating

a brand toolkit and weighing the value of each ele-
ment and thereby deciding which elements are to be
retained and which need to evolve or change.

Colour Typeface

Retained Elements: Brandmark Photography

Brandmark, Infographics, Wipro Disc, Photography

Elements evolved / changed:

Infographics Iconography
Typeface, Colour, Grid & Layout, Iconography

Wipro Disc Grid &

Layout

64.
 Design Odyssey

Atomic design
The elements of this design system is loosely based on the Atomic design principle by Brad Frost. This methodology
divides the design into 5 distinct levels, each built on top of one another.

Atom: An atom consists of the basic building blocks

of the design, these include the colors, typography,
icons, styles, etc.

Molecules: Molecules are a combination of the

basic atom structure. For example combining the
colour, shapes and typography styles can result in
the creation of buttons, text fields, tabs etc.

Organisms: Organisms are group modules joined

together to form a relatively complex, distinct section
of an interface.

Page Templates: The page template is where

diffrent organisms come together to form completed
layouts.

Pages: Pages are the specific instances of tem-

plates. Here the placeholder content is replaced with
real world content to give an accurate depiction of
what a user will ultimately see.

65.
 Design Odyssey

Grid & Layout System

The layout style illustrated in the Wipro guidelines

only applies specifically for print medium,
specifically A4.

Hence we using a scalable bootstrap grid,

designed for the web.

Iconography

The Wipro iconography set does not scale well

when used in small to very small sizes (below
30px), hence we have used the open source
material design iconography as our system
60px 30px 20px 10px default.

! ! ! !
These icons work only at a functional level of the
Quantum system with buttons, fields, etc and
hence do not affect the overall brand perception.

Photography

Quantum follows Wipro’s primary photography

style of monochromes.

66.
 Design Odyssey

Colour

The Quantum colors are derived from the Wipro

brand colors.

Typeface

The Quantum style guide uses Wipro Akkurat

TT and Akkurat Mono TT for its typography
style and hence comforms to the Wipro brand
guidelines.

Header sizes from H4 to H6, use Wipro Akkurat

to prevent cluster and implementation issues at
the table and form levels.

Data visualisation
Deal Count

100

90 Uses the Wipro brand colors and typography

80
along with rounded edge bars and graphs.

70

60

50

40

30

20

10

67.
 Design Odyssey

Quantum colours
The colour palette is divided into 2 parts:

1. Wipro brand colors

2. Quantum system colors

Wipro brand colors

Apple Green Navy Blue Sky Blue Ruby Red Dark Grey Light Grey
#6DC24B #0E3570 #00A2E0 #EF3341 #646363 #F2F2F2

Sunny Yellow Black White

#FFDA29 #000000 #FFFFFF

Quantum system colors

Azure Blue River Blue Metal Light Metal Dark Marble Grey Washed Grey
#2F81FF #D9E9FF #9B9B9B #4A4A4A #D8D8D8 #F9F9F9

Vivid Amber Midnight Blue Assistant Blue

#F58323 #103F86 #E5F0FF

68.
 Design Odyssey

Icon library
Download URL:
https://github.com/Templarian/MaterialDesign-Webfont

We have adopted Google’s material design icon library to use as our default icon set.
Default usage size against 14pt Wipro Akkurat is 20pts

Quantum icon set (sampler)

! # $ & ⋆ * ,
" © % ' ) + -
. / 0 1 2 3 4
5 6 7 8 9 : ;
< = > ? @ A B
C D # E ♥ G H

69.
 Design Odyssey

Drop shadow
We are using 4 different type of shadows in
our design.

Button & Components Assistant Card

drop-shadow - drop-shadow -

Hex: #000000 Alpha/Transparency: 30% Hex: #000000 Alpha/Transparency: 10%

X: 0 Y:0 Corner Radius: 4px X: 0 Y:7 Corner Radius: 4px
Blur: 6 Blur: 10

Rows Rows
drop-shadow (Inactive) - drop-shadow (Hover) -

Hex: #000000 Alpha/Transparency: 10% Hex: #2F81FF Alpha/Transparency: 40%

X: 0 Y:0 Corner Radius: 5px X: 0 Y:0 Corner Radius: 5px
Blur: 6 Blur: 6

Corner radius
The corner radius for all components is 4px
and the border width and width of lines is
1.5px.

Corner Radius - 4px Border Width - 1.5px

Illustrative example: Enlarged 4x Illustrative example: Enlarged 20x

70.
 Design Odyssey

Grid system
We follow the bootstrap
12 column grid.

12 column grids is a conven-

tion and is easy to understand
and works well for most
layouts, and thus, is more
popular.

The reason Bootstrap has a

12-unit grid (instead of 10, 16,
etc..) is that 12 evenly divides
into 6 (halves), 4 (quarters)
and 3 (thirds). This makes
adapting to a variety of layouts
much easier.

Overlap styles

Write Access
7-px
x
60px ! 60/2 =
30px Vertical Head

Nominations start date for Accounts

DD/MM/YY "

Nominations end date for Accounts

Lists Cards
The first row will have an overlap with the However, if the first row or element has a
background layer. height greater than 200px, then only 70px
will be taken as the overlap space.
Where x - the overlap, will be equal to half
the height of the row.

71.
 Design Odyssey

Buttons
Button sizes are dynamic. They can be resized to fit the label or layout.

standard button sizes:

160px width (minimum)
and 40px height (fixed)

As an ideal practice, the button label should not exceed more than 3 words.

Incase the size exceeds 160px, there should a padding of 10px on both sides.

Primary Button Button height: 40px

Corner radius: 4px

Button width: Dynamic

(Follow set sizes for
different cases)

Primary Buttons Secondary Buttons Actions and Navigation

Drop-downs
%

Primary Button Secondary Default ! Alphabetically "

Primary Hover Secondary hover # Search & '

Primary Hover Secondary disabled ( 1

$ Export

72.
 Design Odyssey

Other elements
Standard button size:
120px, 160px

Dynamic scaling column sizes.

Naming tags

SS Tulika Ruth (Digital) ! KB Kinshuk Bose (Designit) !

VR Venkatanarasimha Rajuvaripet !

Space between tags 5px 10px

SS Tulika Ruth (Digital) ! DP Demetrius Pais ! AS Anjaneya Pratiksha Sharma !

10px
Villupuram Chinnaih Pillai Ganesan ! 10px

SS Tulika Ruth (Digital) !

SS Tulika Ruth (Digital) !

SS Tulika Ruth (Digital) !

SS Tulika Ruth (Digital) !

SS Tulika Ruth (Digital) !

73.
 Design Odyssey

Text fields

Text fields Text fields with icons

Prefilled /Hint !

Prefilled /Hint Active field !

Active field Completed field !

Completed field Error !

Error Type your text here !

Error message
Type your text here

Error message Disabled !

Disabled

10px 10px 10px 10px 10px

350px 350px

74.
 Design Odyssey

Text fields
(Grid layout)

Header details

Label Label

Type your text here Type your text here !

40px 60px 60px 350px 40px
20px
Label Label Label

Type your text here ! Type your text here ! Type here #
145px
Label Label Label

Type your text here ! Type your text here ! Type your text here !

Label Label Label Label

Type here ! Type your text here ! Type here " Type here "
60px
Error message
Label Label

Section
Type your text2here
- Buttons & navigation ! Label
Type your text here !
Type your text here !

1250px

%
Service lines + Add service line
10px 10px
Service LIne * Practice * Sub Practice * SL BDM * % of TCV * Est. SL TCV* Cloud Engagment model* Dual credit

40px Digital O... " VS - BFS... " Ref data... " Search # 00.00 00.00 Select " Select " $ !

60px Select " VS - BFS... " Ref data... " Search # 00.00 00.00 Engage... " Select " $ !

Data an... " VS - BFS... " Ref data... " Search # 00.00 00.00 Select " Select " $ !

10px 10px 10px 10px 10px 10px 10px

75.
 Design Odyssey

Column & rows`

Columns & rows

Name ! Number ! Status ! Type ! Owner ! SBU ! Vertical ! Sub-vertical ! Geo !

20px Enter text Enter text Rejected Mega-gama Owner's name SBU name Vertical name Sub-vertical Geo name

120px 120px 120px

20px 20px

Size 1 Size 2 Size 3 Size 4…

Name Name of contact Name of contact/address Name of contact/designa…

60px 120px 180px >180px

Columns & rows

Name ! Number ! Status ! Type ! Owner ! SBU ! Vertical ! Sub-vertical ! Geo !

10px

Name of account Number Rejected Mega-gama Owner's name SBU name Vertical name Sub-vertical Geo name

10px

Name of account Number Approved Mega-gama Owner's name SBU name Vertical name Sub-vertical Geo name

10px

Name of account Number Rejected Mega-gama Owner's name SBU name Vertical name Sub-vertical Geo name

Name of account Number Rejected Mega-gama Owner's name SBU name Vertical name Sub-vertical Geo name

Name of account Number Rework Mega-gama Owner's name SBU name Vertical name Sub-vertical Geo name

Name of account Number Rejected Mega-gama Owner's name SBU name Vertical name Sub-vertical Geo name

76.
 Design Odyssey

Other elements

Toggle Switches Checkbox Avatars - without images Avatars - with images

SS

SS

SS

Radio Button SS

SS

77.
 Design Odyssey

78.
 Design Odyssey

Ideation & pre-design

workshops
• Walkthrough and workshops
• Visual design

79.
 Design Odyssey

01
Pre-design
workshop

Ideation workshop on identifying various roles and parame- - Deal creation

ters that constitutes the DPS. The key points emerged out of
- Deal team formation
the workshop revolved around following parameters.
- Module creation
- Phase creation

Deal creation
A deal is created against an existing opportunity by an oppor-
tunity owner who gets a pre-populated list of attributes once
he provides the opportunity ID and add additonal parameters
to it. The step is followed by assignment of a deal owner.
The deal owner is a person from the presales who manages
the entire deal. He starts forming a deal team consisting of
people from various domains like finance, legal, business etc.

Module & phase creation

Phases are the distinct period or stage in a process of de-
velopment eg. research, development etc., wherein, modules
are the logical chucks of work that a deal owner distributes
amongst various teams. A phase is created by deal owner
wherein he specifies the timeline, name of the phase and set
dependencies* amongst various phases. But creation of
module started with assigning a module owner, who then
assign module team and specify start & end date of the
corresponding module.

What is dependencies?
If completion of task ‘A’ depends on completion of task ‘B’,
then there is a dependency between A & B. And end date for
the task A cannot be assigned before end date of task ‘B’

80.
 Design Odyssey

Phase vs. module

Add phase Module Deal tab in
timeline
button overview panel

Phase vs. module

timeline

Block structure
representing
modules

Paremeter details Business requirement

The parameter level details were provided by business team
after the workshop. These were mostly field details required
in the creation of deal, modules and phases.
1. Modules 2. Phases
Multiple modules and phases need to be captured together
so that the deal and opportunity owner can get a clear un-
derstanding of timeline and work distribution. A dynamic view
which can be source of instant information, capturing timeline
and breakup of SOW effectively.

Module owner Phase name

Module name Start date
Start date End date
End date Dependencies
Dependencies

81.
 Design Odyssey

Ideation Ideation of deal planner over paper was a key towards bringing the
initials thoughts into existence. The exercise took hours to under-
Paper prototyping stand the requirement and build concepts around it. After various
iterations and versions, the final design came into picture.

Change in activity
Graphical view
for phase

Module timeline
view

Card with module

Calendar view
details
82.
 Design Odyssey

Key requirement
Graphical representation for phase activity Module & phase details.

The planner will capture the status of actions against The module and phase information to be shown
the phases and will generate a curve that will show upfront in a UI.
progress.

Version 01

Phase card with

Phase timeline
action status
overlapping
Module phase
overlap

Card with module Add module

details button

Pros Cons
• Easy representation of multiple phases within • The graph cannot be generated for smaller deal -
same module - The horizontal lines depicting the It might not be possible to capture the graph in `
phases can keep on increasing based on require smaller deals
ment. • Timeline overlaps - The overlap of phases can
• Card style for module information : create confusion on timeline understanding.
The module information will be reflected upfront in
a card style UI

83.
 Design Odyssey

Add phase
Version 02 button

Add module
button
Multiple phase Add phase Calendar to show
with colour button the timeline
variations

Horizontal lines
Card with module Start & end date equivalent to
name and owner of a phase` nuber of phases
details

Pros Cons
• Start & end date visibility - The upfront information • Phase at deal level lag details - Phase details like
on start and end date is really effective. start end date, dependencies etc are missing at deal
• Overlap of phases - The colour variation helps to fig level
out the overlap easily. • Add module & phase button - The button visibility
lags with increase in number of modules entry.

84.
 Design Odyssey

Version 03 Zero stage Add phase & module

view button together

Phase name,
number, start & end
date. All captured in
single card

Phase creation
form

Phase 3

Start date End date

09 May 2019 29 Jul 2019

Commercial Model Invoice profile

Commercial Invoicing

Dependencies
Phase 2 Phase 4

Clear colour separa-

Upfront timeline tion of calendar from
visibility for phase the planner
and module

Toolkit on
mouse over
85.
 Design Odyssey

02
Pre-design
workshop

The idea of pursuit calendar to track and manage timlines for Calendar level parameters
deal and related activity was introduced. The calendar will
1. Actions
create action against the requirements of the deal. Calendar
2. Status
is a way to manage the delivery of the commerical and
3. Timeline
techical proposal. It may not be required for smaller deal but
4. Sorting options
for larger deal, since the timelines are extensive and need
5. Action summary
governance, the idea to have a calendar succeeded.

Action creation parameters

Pursuit Calendar 1. Actions name
2. Action Owner & creator
3. Planned start & end date
• Calendar consist of various actions. These are divided into 4. Attachments
tech solutions, commercials and other type of actions. 5. Dependencies
6. Approval required - Y/N
• In a deaal, for every task created in calendar is refer as 7. Approver
‘Action’. There can be various type of actions like tech solu- 8. Escalate contact
tion action items, RLS actions, etc. 9. Description

• The action is created by deal owner and may or may not be

tagged to a module. Parameters like action name, action
owner, creator, start date, end date, dependencies need to to Action stages
captured while creating an action.
1. Pending
2. Approves
• A tech solution related action may/may not requires an
3. Pending with approver
approver. An approver is a team member from the corre-
4. Sent for approval
sponding module team, whose work is to verify, approves or
5. Sent for rework
send action for rework.
6. Reject
7. Escalate
• An ongoing deal can have multiple level of stages ie.
Pending, approved, pending with approver, sent for rework,
reject, etc.

86.
 Design Odyssey

Ideation
Paper prototyping

87.
 Design Odyssey

Version 01

Action bar cap- Calendar

turing start-end timeline
dates

Blue colour shows

action status as Acion owner, Dependencies
ongoing creator details listing

Pros Cons
• Action list - All actions can be access at once • Timeline for all actions will not be the same. In such
due of the listing style case, its useless to show those actions in the list.

• Expansion state - The expansion of action gives • Basic calendar functionalies like filtering via weekly,
sufficient space to show all necessary details like monthly, and yearly basis, scrolling through the dates
dependencies, owner, escalated contacts, approvers etc are missing
etc.
• There are various stages of action. It is hard to
identify them here.

88.
 Design Odyssey

Version 02

Calendar Action list with Calendar Specific action

expanded name and time- timeline settings
view line details

Start & end

Collapsable date captured
actions groups via bullets

Pros Cons
• Calendar view - With actions created in calendar, • Stages - Various stages of action like pending,
it allows the collection of date and time-based approved, rejected, ongoing etc are not visible
information in a single place for multiple members upfront.
to access and coordinate.
• Sorting - Calendar sorting like weekly, monthly, and
• Collapsable tab - The collapsing of related action yearly basis view should be highlighted.
type will make it easy for user to see only the relevent
actions at any instance.

89.
 Design Odyssey

Version 03

Calendar Calendar Toolkit Current Toggle Create action

sorting timeline stage day between list button
and graph view

Collapsable Completed
action listing action shown Action Ongoing
as green stages summary actions

Weekly view

Toolkit showing Approval Rework

action details stage stage

90.
 Design Odyssey

Action creation form

The action creation form appears on click of
creation action button. The user is provid-
ed with the parameters in which some are
mantadory and some are non-mantadory.
This step in turns create an action bar in the
calendar which shows the start and end date.
As the user progress, the stage of the action
changes from ongoing to approval to rework
to approved.

Below is shown various stage of action and

how it changes on proceeding ahead.

Actual Sent for Sent for Sent for Approved Planned

start date approval rework approval & actual end date
end date

Approval stage Rework stage Approval stage

91.
 Design Odyssey

List view
The toggle option between list view and graph view is an effective way to provide user
with multiple approach to the action. The list enables them to get concise and detailed
information directly.

Action Action parameters Create

listing from the form. action

Action related op-

erations, based on
Deal Owner various roles.
A deal owner will get the opportunity to
edit, download and delete any action.

Action owner (action without approver)

An action owner with a deal which do not have an
approver will get the option to approves any action them-
self and a download button.

Action owner (action with approver)

An action owner with a deal which have an
approver will get the option to send doc for approval.

Approver (pending approval)

An approver who is sent the doc for approval can either
approve, send for rework and download the document.

Approved actions
An approved action list will show only the download
button to the users.

92.
 Design Odyssey

Pursuit calendar - Graph view mockup

93.
 Design Odyssey

03
Pre-design
workshop

Tech solution
A repository for list of documents created to fulfil client Tech solution parameters
proposal requirement. A document creation in tech sol will 1. Document name/ Section name
directly create a corresponding action in the pursuit calendar.
2. Approver
A document is generally break down into sections and
subsections and are assigned to various modules owners 3. Author
4. Module
5. Start End date

Organising documents in a tree structure to indicate 6. Escalate contact

hierarchy. This will help users navigate to section and 7. Attachment
quickly find a nested child section without loading
each sections while navigating to the final destination
sections.

While ideation, we dig deeper into all of the following

stages of tech solution creation.

- Document/section ideation
- DA content push
- Checkin/checkout functionality
- Approval rejection and rework
- Collaboration platform

94.
 Design Odyssey

Ideation
Paper prototyping

95.
 Design Odyssey

Tech solution
form

Tech solution
creation form
A tech solution form consist of parameters
like document name, module, author,
approval, attachment etc. These fields
helps in formation of a document list
under tech solution listing. Based on the
complexity of deal, a document can be
further divided into multiple sections and
sub-sections.

Document Tech solution Scroll tab to

hierarchy parameters navigate to other
fields detail

Approved
document

96.
 Design Odyssey

Assistant and collaborate

worktogether inside DA

Digital assistant
A digital assistant supports the user with
the recommendation and suggestions
based on the requirement. The assistant
in tech solution provide the user with the
strawman structure based on the type of
deal.

The DA provide suggestion for

document and section names. Also it Proposals from past will
provide you with the content type. Any help in populating content
efficiently
combination of doc and content can be
use to create the strawman.

The assistant provides feeds on past

deal of similar type and provide
suggestions.

Content can be Similar deal in past can

pushed from similar suggest the strawman
deal directly to the structure and hierarchy of
selected document. document, sections and
content

Multiple structures to
chose from

97.
 Design Odyssey

Collaboration
platform
An effective collaboration section wherein all the team
members can work, manage and track down the activity
and requirement against an assigned task

Check In / Check out

• Document management systems 
• Prevent conflicts in an environment where multiple people might want to edit the same piece of content
• Check-in - The process of adding a new or modified item or file to a document library or a list to replace the previous version.
• Check-out - The process of getting a version of a document or list item in a list or library.

Chat feature
• During a chat an agent can request the customer
upload a file attachment to be sent to the agent.
• Inbound messages can optionally display the
customers avatar.
• Consecutive messages only display name and time
meta data once

Key Interventions

- Chat/comment functionality
- File versioning
- Checkin / checkout feature
- Maintain log of past comment and attachment.

98.
 Design Odyssey

Update in Chat Attachment

status functionality history

Check In / check Out

button

Versioning of
documents

99.
 Design Odyssey

Collaboration platform - Mockup view

100.
 Design Odyssey

Deal planner - Mockup view

101.
 Design Odyssey

Learning
My engagement with designit throughout this internship helped me to grow along with the project.and understand the
nuances of working in team. Project quantum let me explore and exhibit my capabilities to the fullest. Working with the
team of engineer, business, and finance helped me to widen my thinking capability and take a new approch wherein I
not only considered every challenges but also design for everone. Understanding and being the part of WIpro’s internal
project brought many new prospect to my learning, wherein I started consuming resources from business, tech, finance
and various other services. This experience being just merely an intern was highly vauable and great foundation to my
career ahead.

102.
 Design Odyssey

Bibliography
1. CONFLUENCE - DIGITAL PLATFORM FOR DELIVERY confluence.wipro.com
2. List of 10 Best CRM Tools - Financesonline.com financesonline.com
3. I Used The Web For A Day With Just A Keyboard — Smashing Magazine www.smashingmagazine.com
4. How to Conduct a Cognitive Walkthrough | Interaction Design Foundation www.interaction-design.org
5. Deal Management | Opportunity Management | Zoho CRM www.zoho.com
6. Organizational Structure of Wipro -- brainmass.com

103.
Design Odyssey
Design Odyssey

Department of Fashion Communication

National Institute of Fashion Technology, Bengaluru