NCR Critical Reflections


My experience at NCR as a whole provided a great deal of valuable insight into the inner workings of a corporate business. However, as can be expected, there were both positive and negative factors to the overall experience. This section will detail my experiences and discuss my reflections on several aspects of my time at NCR Dundee.


Management of workload

At the beginning of the Socially Mobile project I decided to follow a hybrid form of the Double Diamond design process with certain service design methodologies used throughout. This process plan acted as a successful tool for keeping me on track and could be easily altered as my process become more informed. As a result, my process plan evolved as the project developed.

  1. Framing (Me) (find out what the problem is and what stakeholders are involved)
  • Objectives and research questions
    • What is the problem and who does this problem effect?
  1. User insights (Users) (find out who is/isn’t communicating and how they do so)
  • User Journey Map (Satisfaction & Actors map)
    • A map of the individual stakeholder’s interaction to the service journey. The map will include individual satisfaction and actor touchpoint maps. The researcher will then ask the stakeholder what they felt the reason was for each of their highest and lowest points.
  1. Personas (Users) (Find out how to best appropriate the design for each stakeholder)
  • Persona and User Analysis
    • Discover what each stakeholder’s service attitudes are, are they leading there section or are they lead, are they the controlling stakeholder or are they submissive? The persona will also detail the individual motivations and demotivations of the role they play. An understanding of the tools they use each day will allow for an understanding into how to best position the end output, be it an app or another such service.
  1. Design scope (Me) (define a clearer image of the challenge and objectives)
  • Design Challenges
    • Rework the initial objectives, given the new insights. What is the service that needs to be improved? Who are the key stakeholders? Describe the measurable goals of the service and finally state the newly honed design challenge.
  • Design Requirements
    • Considering the new design challenge, what are the highest level goals within the Physical (usage environment), Active (activity’s and operations of use), Emotional (non-functional), Relational (interactions with other), Tangible (physical item) and Rational (functional) contexts? Select the most important requirements that will make the most difference if offered a good answer.
  1. Ideation (Me) (develop several ideas and condense them into viable concepts)
  • Inspiration Blossom
    • Place the design challenge in the centre of a page with the main requirements arranged around it. For each requirement, select a current example of a product/service that acts to fulfil the requirement. Think about why this example is effective and write the reasons down, arranging them around the example product/service. Finally combine the best properties from the examples into ideas for the future service.
  • COCD Box
    • Once you have collated all the ideas from the previous exercise place them into their corresponding CODA box. After you have assigned each idea you will be able to now categorise them into ideas to “forget about”, “look to later”, “consider” and “may include”.
  1. Concept Refinement (Me) (speculatively illustrate the top concepts in action. Do they address the issue?)
  • Concept Storyboard
    • Now create a storyboard for those ideas that seem to be the most valuable, considering all the key stakeholders. Acknowledge and state the activity and any touchpoints that may be made in each scene, highlighting any potential pressure points.
  • New Speculative User Journey Map
    • Create a journey map that considers the actor touchpoints and if the concept would work effectively considering all the key requirements.
  1. Prototype and test (Users) (Test the concepts and analysis there use)
  • User Satisfaction Map
    • Create or get the user to create a satisfaction map that highlights the individual pressures and satisfactions whilst using the service concept.

The plan can be divided up into the four categories of the Double Diamond process:

  • Discover – Steps 1-3
  • Define – Step 4
  • Develop – Steps 5 & 6
  • Discuss – Step 7

I found that applying most focus on the discover stage was of great value as it allowed me, as an external observer, the ability to gain insights into NCR as a company and the individuals it employs (my user group).



The greatest challenge that I faced was the general corporate culture and the issues that related to it . I speculate that the challenges I faced are typical of most large international corporations and I do not believe them to reside solely within the NCR Corporation. However, the related issues affected my process dramatically whilst fortunately also educating me in how to better my research practice.

In the initial stages of my process I developed a short interactive questionnaire  that I disseminated to my identified user group, to better understand what role each participant played within the ATM service delivery journey. This initial dissemination yielded no results and so a follow up email was sent to all those that were invited to participate. It was quickly identified that I was most likely not going to receive any responses and so the document was re-disseminated by other members of the UCD team at NCR, in a hope that the invitees would respond to a higher level within the NCR hierarchy. Even this attempt yielded no response and after several varied attempts I re-evaluated my focus and began to find the information by other means. This company wide lack of cooperation was indeed the greatest challenge that I faced, a challenge that has been flagged to NCR as one of my greatest insights. This challenge helped me to learn that not all people are as eager to provide help as I originally perceived and that there may be a flaw in the means at which I designed the original questionnaire.

I overcame this cooperation challenge by targeting key individuals within NCR and asking a few specific questions within a semi-structured interview setting. I was able to target and interview key people internationally, that gave me great insight into their specialised field. With the information I gained I was able to inform the continued development of my process.



My main points of contacts within the NCR Corporation were the User Centered Design (UCD) Team; of whom I met for discussions and feedbacks sessions regularly. The wide range of design skills that the UCD team provided, allowed for a thorough review to be conducted whenever I required peer input. I also liaised with international NCR specialists on a regular basis, these interactions allowed me to build a greater understanding of the design requirements and how to best address them.  Most of these discussions took place over the phone and were arranged in a semi-formal interview structure; this allowed me to ask for further detail on discussion topics and created a deeper connection with the participant, allowing for follow-up questions to be asked later. Around roughly half of those that I invited for an interview accepted my offer in some way, even if it was simple an email reply to my questions, and so I had a greater deal of success via this communication technique than I had had in the past using my insights questionnaire.


Project Output

It was clear from the beginning of the placement that those that had issued the original project brief did not truly know what the final output would look like. Due to this I began the project with the mind-set that I would concentrate on the Discover stage of my process before I thought about what form the project would take. It was quickly noted that after the first two weeks, and after my first progress presentation, that my placement supervisors had begun to think about what form they desired as an output. The term “App” was stated on several occasions during my presentations and potential outcomes were usually discussed in more depth after each meeting. In my experience, I have always found it to be counterproductive to ideate before you have all the information necessary to feel comfortable in the development of a design solution. I found the constant ideation discussions quite distracting, it was subtly noted that my supervisors wanted a digital application output from this project.

The disciplinary field of digital application design is relatively alien to me, I have had limited interaction with those that practice the skills but have not every partook myself. This aspect of the project resulted in a new challenge that in turn resulted in a notable educational experience for me. As a first time application designer with a limited time scale I decided to use an online application prototyping tool called “InVision”. This tool would allow me to stitch together several PDF images in an attempt to mock the functionality of my application designs. I used my graphic design skills to develop several 2D layout designs and then used “InVision” to stitch them together. The resulting prototype displayed the basic functionality and graphical elements of the finial concept. I was informed by placement supervisors that the outcome was impressive and that it demonstrated all the aspects that they wanted to see in the final output. I consider my efforts as a success and I am a happy with the learning process and skills that I developed along the way. Through this experience I learned how to create basic application prototypes and gained further knowledge into how a digital app should be developed. Through discussions with a NCR senior interaction designer I learned what aspects of the prototype I had completed well and others that I needed to improve on.


Greatest Success & Failing

My overall process consisted of several successful aspects as well as several unsuccessful ones. Interestingly my greatest success and failing are interlinked. From discussing my outputs with my placement supervisors it was raised that my greatest weakness was the lack of cooperation that I faced with the company, however this was also my greatest finding. This finding is mutually beneficial for me and NCR as the UDC team now have evidence that certain research techniques do not function with certain user groups and I have acknowledged that failing in one aspect can result in new insights in another. I believe that my process was overall successful as it functioned well in keeping me on track and I did not loose direction. However, the initial stages were complex and user feedback was quite weak. Using this experience to further my development, I now know that I applied to much focus on the early stages (stages 1–3) and not enough on the later (arguably more important) iterative development stage (stage 7).


Personal Improvement

There are many ways in which my experience has acted to improve my abilities and many ways in which I can see it informing my future work. The major aspect of my experience that I will carry forward is user consideration. I believe that my initial insights questionnaire failed in part due to its overall design, considering both design language and scale of ask. The questionnaire was developed early in my process, without too much insight into the work that the targeted users groups are used to. I speculate that the “Insight Toolkit” document appeared alien to the user groups and without any incentive, there was no desire to complete the task. This combined with the fact that the document consists of eleven pages could have acted to deter the user from completing the task. I have since researched ways in which I could have condensed the content and made the task more desirable. I acknowledge that my main failing was that I was asking for all the information I desired and not considering how that focus could affect participation. From this experience I will be much more considerate in the future in how I ask questions and how I design the content to improve participation.

During my placement I also worked on developing skills in application design, from doing this I have built my confidence in prototyping applications and have gained a further understanding of their development. I see this as a valuable skill as the digital world is growing rapidly, and an understanding of how to apply my design skills to this field will soon be a necessary leap.

Additionally, all the experiences I have gained in relation to corporate culture and industrial design within an international corporation have added to my knowledge base, acting to inform my future work. I now have a greater understanding of how to appropriate my design skills to new user groups as well as how to address and communicate with those that I seek information from. I have gained industrial design skills such as how to complete a competitor product review, host live user trials and complete R&D tasks. All these new found skills can feed into my future work and will act to boost my currently active abilities.



To conclude, my experience at NCR Dundee has had its road blocks but has at no point hit an educational standstill. Every fall back has resulted in a lesson learned and every success story has helped to aid in my further development. I am pleased to have had the opportunity to spend time within a corporation such as NCR and will carry the experiences forward into my future design work.

cover image 1
Hero image detailing the NCR Voice mobile application in use.


Paper Based Sketch Prototyping

In order to best visualise how the platform will function I developed a paper prototype of each interface within the general applications functionality. I completed this task for both a mobile and web based application (these can be seen below). Through the development of these paper prototypes I am able to traverse through the applications and test the functionality. This was an iterative process and each time I went through the prototype’s interfaces I was able to determine if there was any missing steps that would help with the flow of the interaction. This process was also a great learning exercise to see what aspects worked visually and what aspects, such as social capital, looked like when translated into a tangible interface.


2016-07-27 14.09.43

I now intend to digitise the application design and subject it to review by some of the UCD team. I suspect that in the next week or so I will be able to test the basic functionality with users online.

Prototyping: Mobile and Web Application Map

To really understand what the platform would look like I decided to map out the interaction functionality for both a mobile and web based application. Both maps host similar functionality however content review and text based input aspects, are stronger on the web based display due to the benefit of having a large screen and additional input functionality (keyboard etc…). The web based system also has additional functionality in the form of an admin section. This section is for those within the product development team that govern the customer/consumer insight gathering aspect of the platform. Due to the additional capability that are available on a computer (web app) in comparison to a mobile device the admin aspects may not be available on a mobile device, this conundrum is still under discussion however.

Mobile Appliocation Fuctionality map-page-001 Web Appliocation Fuctionality map-page-001

I now intend to sketch prototype the aspects of the maps that can be seen in this post. I will then sue these sketch prototypes to ask for further advice on the platforms development.


Now that I am nearing the third chapter of my time at NCR, I have begun to venture into the ideation stage of my design process. For many weeks now I have had ideas rattling about in my head and it’s a relief to finally put them down on paper. I have organised my ideation into two categories, Must Have Features and Concept Cores:

Must Have Features

The must have features have been realised from research into both the suspected users, and currently used products.  It is of great importance to consider both these elements as without them the service could be either unfamiliar or not appropriate to the user. The five speculatively diagnosed features can be seen below:

  1. Custom homepage
  • In order to build a relationship between the user and the platform and to encourage continued use and gamification.
  1. Personal profile generation
  • To encourage use through the building of social capital and ego incubation. The use of a profile will also help to facilitate an informed user allocation system through the building of each user’s skill sets.
  1. Incentive system
  • In order to maintain willing participation and a gamification aspect to the platform. The reward system will also play on an already familiar system that exists currently with the NCR culture.
  1. Idea box or managed question system
  • A system that allows for the users to either offer their own insights freely or a system that allows for the facilitated governance of an allocated question system.
  1. An IM system
  • A service that allows for instant communication across the platform, this will be useful when discussing a topic between peers.


Core Concepts

I have developed four concept cores from the information I have gained over the past weeks. A concept core is an idea that has no physical form, and instead purely details the ideas intention. The below concept sheets demonstrate what each of the concept suggests, utilising a relevant image, 100 word description and the pros and cons of the general concept. See below:

Disscussion Platform-page-001 ideas box-page-001 Managed Quistions-page-001 positive feedback-page-001

I next plan to whittle these concepts down into my main concept and to create a visual map of how it will function. I will then intend to sketch out what each feature is and what it could look like. After doing this I would like to get everyone within the UCD group together to review and critique the concept.

Inspiration Moodboard

Below, you will see a selection of images that demonstrate what the market looks like in regards to my project direction. The images that can be seen below are all examples of communication platforms and mobile note taking applications. I have used these examples to understand what features are popular within the market and to try and make sense of why that is. I intend to us these images as inspiration during the concept ideation stage of my process.

Inspiration – Lotus Blossom

In order to understand how to address my design requirements, I decided to use a design tool called a Lotus Blossom. This tool asks for the user to gather the 8 most desired requirements for a design outcome and find a currently existing example that addresses the requirement very well. The user is next tasked to give eight reasons why this design is so effective at meeting its given requirement. The end map when presented visually appears as a blossoming flower, hence the name. A textural copy of my lotus blossom can be seen below, detailing the requirement, the example and the 8 reasons why the example is so effective.  An image of my Lotus Blossom can also be seen below:



Facebook & General Social Media

  • Self-esteem booster
  • Allows for self-promotion
  • Helps maintain relationships
  • Gives a sense of belonging
  • Selective self-representation
  • Builds social capital
  • Has a massive following
  • Allows for the gathering of information


Mobile Phone

  • Can cater to your every need
  • Small in scale
  • Allows access to constant information
  • Applies a sense of security
  • Can allow for the ability to integrate through information gathering
  • Allow for you to connect to ay one anywhere
  • Has new emerging functions, innovative
  • Can be worn as an ego boosting accessory


Phone Number pad and keypad

  • It is universal
  • Has an unchanged design
  • Works of the current user knowledge
  • Doesn’t have excessive information
  • Is not over designed
  • The market is used to it
  • Caters specifically to its market segment
  • Limited competition


Twitter and general social media

  • Allows for the control of content
  • Can be self-managed
  • Facilitates communication on a level playing field
  • Is not industry specific
  • Customizable home pages with a choice of themes
  • Only get the content that the users asks for
  • The platform is very simple and only offers basic functions
  • Everyone can say what they want


Apple IOS

  • Show transitions, to make sure the user knows where they have come from
  • Use breadcrumbs to detail where the user has come from
  • Instead of having empty areas, offer subtle example of how to populate the area
  • Consistent design throughout
  • Offer shortcuts but don’t make them essential to follow
  • Use current patterns that the user is used to
  • Less = more
  • Don’t tell the user what to do instead subtly hint at them direction to go in


Apple Pay & Google Wallet

  • Uses a product that everyone carry’s with them at all times
  • Reduces the effort taken to complete a transaction
  • Removes the need to carry around any additional products such as credit/debit cards
  • You do not need to remember a pin number, it works on biometrics
  • Reduces transaction time
  • Can send money to anyone from your phone, a feature you can’t with the current solution.
  • The service journey is built off of an already existing system that was in place for cards
  • Simple step by step process



Google Analytics 

  • Can be lined to other services to add other functionality
  • Organises the data gathered into visual representations
  • Organises the data into categories without any user interaction
  • Is made up of multiple levels so you can get as little or as much specific data as you require.
  • It is a freely accessible tool
  • Still requires a user interaction to deliver full functionality, allowing for insights to be made
  • Doesn’t offer specific data as standard, allowing for the system to be simpler to understand.
  • Offers the ability for the user to display the most Important info, to them, first


AudioNote Lite

  • Offers real-time voice recording
  • Offers note taking that are timestamped to the audio recording
  • Allows for the addition of images in the notes
  • You can add notes or other content later to support the audio track
  • If the user is to tap on the notes it takes them to the point in the audio recording that the notes were taken in
  • The app highlights the notes as you are playing the audio track, to allow for the audience to see what the user was thinking during the conversation.
  • The contact can be shared with others across many device mediums
  • It is a phone app and so is very portable and accessible.


I now intend to begin the ideation stage of my design process, using the 64 features above as inspiration. During this next stage I intend to develop a large quantity of ideas, and using a brainstorming exercise I will then individually analyse each ideas using a COCD Box technique.


Design Scope

Now that I am coming up for the halfway point on this project I thought it valuable to have a Re-analysis of the design scope. The design scope included such aspects as the design challenge, the design objective, the predicted users, KPIs, barriers and the design requirements.

The Objective

To gather the insights of NCRs key stakeholders by bridging the gap between those that drive the product development, and those that interact with the finished product.

Predicted Users (and what they offer)

Riggers – by feeding in the insights from the first customer interaction with the product as well as any installation issues that they personally may have.

Customer Engineers – by feeding in the customer complaints they receive regarding the servicing of the machinery. If there is a regular occurring fault this could be fed into the system.

Accounts Team – if there is any special requests or questions about the future of the industry the accounts team will be one ones that are asked. This information could be fed into the system to inform the company of any questions that the customer is starting to ask.  Accounts will also be the first person that the customer comes to if they have a problem with the current or old products.

UCD Team – Will manage the service/product in order to facilitate the exchanges of information between the development team and the customer facing stakeholders.

The Design Challenges
  1. Providing an effective incentive for the users
  2. Finding a way to maintain continued use of the service/product
  3. Making sure that the service/product can be used by all transitionally
  4. Making sure the correct amout of effort is being implemented to receive valid content
Most Important Measures of Success (KPIs)
  1. User Satisfaction: an increase in the satisfaction of the users.
  2. Resolution Timescale: the speed of resolution when acting on a gathered insight.
  3. Actionable Insights: quantity of insights gathered that can be actioned on.
Design Requirements

I split the requirements into three separate fields, seen below, and asked myself what the most important requirements are for each of the sections. I then selected 8 requirements at the end as the most important. The final 8 requirements will then be used to develop a lotus blossom (design technique).

Physical – Usage Environment

  • Portable
  • Transferable
  • Accessible

Relational – Interactions with Others

  • Transferable
  • Unobtrusive
  • Unbiased
  • Simple
  • Clear

Activities – Operations of Use

  • Simple
  • Intuitive
  • Familiar
  • Comfortable
  • Manageable

Emotional – Non-Functional

  • Enjoyable
  • Motivating
  • Clear
  • Intuitive

Rational – Functional

  • Accessible
  • Clear
  • Informative
  • Supportive

Most important Requirements (in no particular order)

  1. Manageable
  2. Portable
  3. Intuitive
  4. Familiar
  5. Motivating
  6. Transferable
  7. Unbiased
  8. Accessible

The next stage of my process is the ideation stage. I will now begin to develop some ideas around a potential outcome to solve the project objective. Considering all the above aspects I believe I have an effective grasp of the challenge at hand.

Insights Toolkit Update

After the initial development of the “Insights Toolkit” I asked the design team here at NCR to have a look over the content and recommend any changes that they felt necessary. I was given several recommendations about the general content, mostly revolving around the impression that the participants would find certain aspects confusing. I have since altered several aspects of the toolkit and added some further pages, in an attempt to make it easier to follow. The images below show the pages that have been added. please also find a link to the full PDF here: Socially Mobile – Insights Toolkit

Socially Mobile - Insights Toolkit-page-003 Socially Mobile - Insights Toolkit-page-004 Socially Mobile - Insights Toolkit-page-005

My Design Process and Developing a Toolkit

Over the past few days I have been working to create a plan of action in terms of mapping my design process for this project.  Below you can see a 6 stage development progress that will take me from insights to user testing and completion. I simple version of the toolkit can be seen below with the 6 stages and the tools I intend to use in each section:

  1. Framing 
  • Objectives and research questions
  1. User insights and Personas
  • User Journey Map (Satisfaction & Actors map)
  • Persona and User Analysis
  1. Design scope 
  • Design Challenges
  • Design Requirements
  1. Ideation 
  • Inspiration Blossom
  • COCD Box
  1. Concept Refinement 
  • Concept Storyboard
  • New Speculative User Journey Map
  1. Prototype and test 
  • User Satisfaction Map

After I had developed the above structure, I completed the first stage (a quick few questions). I then began to design the tools for the second section; this section involves getting the stakeholders to interact with the toolkit itself.  Once I had sketched up the designs for the tools I planned how I would create them using the Adobe suit (when I gained access to it next).

2016-06-15 16.06.32 2016-06-15 16.06.42 2016-06-15 16.06.53 2016-06-15 16.07.05