DesOps : the Next Wave in Design (Part 3) The Maturity of Design Systems

To understand where a DesignSystem  of an organisation stands in context of implementing a DesOps, first step is to evaluate the existing DesignSystem that is in place and contributes to the organisation’s design process. (We will explore the process aspect in details, in later articles in this series.) To evaluate any DesignSystems  in a broadway we can easily form a metrics that takes care of the following two perspectives on the system.

Designer System Types

Typically the Design Systems can be broadly categorised into 3 types, namely: StaticDynamic and Generative :

Static: Most of the attributes and elements that make this system is mostly static in nature. For example in a Static type Design System, the style guide may be pre-defined print ready reference, defining basic color standards and typography etc. The user has to read through and manually refer it to decide those related attributes in his work. This kind of System mainly prescribes guidelines, rules, principles which does not automatically change or created in a dynamic way either in the stages of creation or implementation by the developers etc. Typical organisational style guides, or UI pattern documentations where the system describes how and where to use the patterns with some sample code to refer are falling under this kind of categories.

Dynamic: This kind of DesignSystem  have the content as well as the principles of implementations are designed and developed in a way that can be directly used in the code. The creation and implementation of the content are dynamic and mostly geared towards the actual elements that can directly be used in the code. This kind of DesignSystem  is more than a reference system for the developer, rather as a part of the actual build of the actual products developed as a part of it. Most easily noticeable traits of this kind of DesignSystem  is that some special purpose frameworks, code libraries are part of it, which integrate into the actual builds of the products.

Generative: Generative DesignSystem  are the ones, which generate the actual build ready outputs that can directly go into the build of the product. For example, instead of a static style guide, a generative DesignSystem  can have the tool that will generate dev-ready HTML, CSS and Java Script based output from the designer/developer inputs. The output of such system, take care of the context for which the design outputs is needed. Let’s say if the developer needs to build a cross platform hybrid app, hen such system can generate the code that will take care of the scenarios for the interaction and behaviour for all target device resolutions, screen density as well as the behaviour for native wrappers as well as in-browser functionalities and restrictions. We will again journey into the details of the Generative Design Systems shortly.

Designer System Maturity 

The other angle to look at the Design Systems is to scale the maturity to measure how much the system has evolved. One of most important aspect of any Design System is to understand the maturity of it, as this helps to understand where it is in the overall DesOpsroadmap. Irrespective of the varied and complex categorisation of the same, we can still name the maturity as Low , Medium and High to get a quick and easy comprehension. And when we try to map the maturity, it takes care of the categorisation aspect.

Low Maturity: When the Design System has a low maturity, it mostly depends on the static attributes that we discussed above. The creation and maintenance of different attributes are mostly the result of manual effort and the most interesting point about this is that the designer and developers have the cognitive load to refer and comprehend and take decisions on what to use and not use in specific context of their work or product. It is also important, there may be some attributes which might have dynamic attributes , but most of them are out of the transition that the design system is having due to its evolution,

Medium Maturity: In the Design Systems  with medium maturity, the most elements and attributes are mainly dynamic in nature. These systems mostly depend on the frameworks, libraries etc. There may be some overlaps in static and well as generative attributes.

High Maturity: Similarly in Higher maturity, apart from the fact that it mostly contains generative attributes, it involves the aspects of automation, computer-vision and may deploy artificial intelligence (AI) to provide continuous pipelines that aspires to remove the human intervention form the process blocks. On ground reality it might require the human intervention to feed in the creative juices or decision power that impacts critical human needs or contexts.

When we map these 2 perspectives horizontally and vertically, we get the the right insight into the DesignSystem’s position in the graph that allows us to clearly understand where the gaps are for the DesignSystem to evolve on which dimensions.

Note that the metrics that govern the success of a DesOps implementation is almost synonymous to this metrics we explored about Design Systems. The factors that adds to this metric on Design Systems,  includes aspect where we measure how impactful the Design System is in touching the different design process lifecycle blocks where each role like an Information Architect or an Interaction Designer , Visual Designer or even the Developer are attached to, in the delivery track. This aspect is more figuratively termed as a Living Design System. 

The Living Design System

The scaling of design is a classic issue. Moreover in recent times the explosive growth of technology across different devices, platforms and ecosystems, it became an ever-growing monster that every designer faces sooner or later. Native (Windows, Android, iOS, Linux etc. ) Web (HTML, HTML5, CSS, CSS3, JavaScript and frameworks etc. ) Along with the combination – the Hybrid – make the scaling of the design language an unending challenge.

The Salesforce design team tried to solve the challenges of applying similar designs across cross-platform product families by introducing a dynamically configurable design asset system which viewed the individual entities of any design system as design tokens.

Technically it was a single JSON file that was the “Single Source of Truth” that contained a set of name-value pairs that defined the properties and their relationships under different categories like text colours, backgrounds, border sizes, font sizes, etc. This JSON was consumed by the framework (i.e. The Lightning Designing System link: https://www.lightningdesignsystem.com/downloads/) developed and templatized for different target platforms, devices, Operating Systems etc. The Lightning Designing System framework generated different formatted outputs for CSS via common CSS preprocessors like Sass, Less and Stylus. Also there was an output in XML format that is supported in Android and JSON for iOS specific development. The Salesforce Design Tokens open-sourced at https://github.com/salesforce-ux/design-system.

The second interesting aspect of this was the use of GitHub to host the design system. Unlike the design system of traditional organisation, where the design system was hosted as downloadable form (even in the cases where the version control like Git is used) these have to be either translated into desired formats for the target platform or hosted especially along with the code. But here the design tokens representing the styles definition and the properties, as hosted on GitHub, were directly integrated into the build process contributing to the Continuous Integration and Development approach of development. In this sense, it was more as a Living System acting a single source of truth, from which the required branch is pulled and be made as a part of the build.

Many other pattern library and/design systems like RedHat’s PatternFlyhttp://www.patternfly.org is also available in similar approach at GitHub (i.e. at https://github.com/patternfly )as that of this second aspect we discussed now. But the idea of making the style guide being available as a SingleSource of truth in combination of this second aspect is what makes the case of the Salesforce design system unique among similar attempts for an approach to deliver a consistent design across different platforms.

(c) 2018, Samir Dash. All rights reserved.

Advertisements

Re-imagining Beta Testing in the Ever-Changing World of Automation.

Based on the paper on the Beta Testing presented at RedHat QE CampX , Bangalore on 7 Dec 2017

Beta-Testing fundamentally is all about ‘A test of a product performed by real users in the real environment’ — and of course, there are many tags we use to refer to the testing of similar characteristics like User Acceptance Testing (UAT), Customer Acceptance Testing (CAT), Customer Validation and Field Testing (more popular in Europe) etc. Whatever the tag we use to represent all these testing cases, the basic components are more or less same — it involves the user testing and front-end UI as well as UX related testing to find out potential issues and rectify. Also, this always happens in the iteration of SDLC where the idea has transformed into a design and has passed the development phases where mostly the unit testing and integration testings have already happened.

Basically, the Beta stage of the Product Life-cycle Management (PLM), is the perfect opportunity to hear from the target market and plan for the road ahead.  When we zoomed into this phase of testing it has a board range of spectrum that ranges from Front-end or UI related testing involving UI functionality, Cosmetic, UI level Interaction and Visual look and feel at one end to the User Experience (UX) at the other end including User Testing involving more from A/B (Split) Testing , Hypothesis, User Behaviour tracking and analysis, Heatmaps, user flows and segment preference study or Exploratory testing and Feedback loops.

Beta Testing has the popular beliefs on the dimension of goodness that defines the typical tools that enable the user to carry out such tests, namely — Shortening of beta cycles, reduce time investment, increase tester participation, improve feedback loop and the visibility etc. However, if we dive deep into the factors behind the existence of tools from different angles, we will find two major reasons that advocate the importance of Beta Testing.

1. Left-Right Brain analogy that points out to the overlap of Human and Technology.

The typical belief is that the left-hand side of the brain mostly processes the logical thinking whereas the right part is more about emotional parts of the thoughts. Based on this popular analogy, when we map the different aspects involved in different stages of SDLC for a digital product across a straight-line from left to right, (refer to the diagram below) we will notice the logical and more human-centered aspects are divided by an imaginary line from the center. We will also notice the gradual progression of the emotional index for the components from left to right.

And when we map these to the beta testing phase, we notice these right-hand components are predominant in such testing phases. As users, as the humans, of the products, we are more emotionally connected to such aspects of the product which are validated or verified in a Beta Testing, thereby making Beta Testing as one of the most important testing phases in any SDLC.

Another interesting point to note here that when we look from the traditional software approach to define “criticality”, the areas that are tested during UAT / Beta, mostly fall into Class 3 and 4 type of criticality. But because these touch the core human aspects, they become more important.

To illustrate this here is a nice video https://www.youtube.com/watch?v=-jHDyhJdDb8that reflects the importance of technology touching the human emotions. This YouTube video posted was a popular brand that offers a glass for the color-blind people which can correct the colorblind vision issue in the real time for the end user. Interestingly this aspect is about “Accessibility” that is one of the aspects that is typically covered during a Beta Testing. Just by looking at this aspect “Accessibility”, in context to the video, naturally, the question comes “What can we do for this father and the son, as a tester or a developer or a designer?”. And when we look at the stats, we find the number of people the accessibility impacts are huge– Every one in five-person is challenged by some kind of disability. But unfortunately in some reports indicate that at more than 90% of the websites in 2011, were not conformant to W3C’s accessibility guidelines.

This itself shows the human angle, that advocates why Beta Testing is important to ensure these aspects are validated and verified so that the target user needs are fulfilled and not go unattended.

2. From the standard’s perspective – Evaluating from ISO/IEC 9126-4 (2001) dimension that defines the difference between usability and quality as a perceptive line.

The International Standards Organization (ISO) has been getting the standards around Quality vs. Usability evolved over time. During the 1998 ISO identified the efficiency, effectiveness, and satisfaction as major attributes of usability. Just a year after that, in 1999, the quality model proposed involved an approach to measure quality in the light of internal software quality and external factors. In 2001 the ISO/IEC 9126-4 standard suggested that the difference between usability and the quality in use is a matter of context of use. The ISO/IEC 9126-4 (2001) standard also distinguished external versus internal quality and defined related metrics. Metrics for external quality can be obtained only by executing the software product in the system environment for which the product is intended.   This shows that without Usability / HCI in the right context, the Quality process is incomplete. One interesting point to notice here that that “context” referred here is actually that is fundamental to a beta testing i.e. “real users in a real environment”, thereby making the case of Beta Testing stronger.

Now we know why the Beta testing is important, let’s explore the challenges that are involved with the Beta stage.  If we notice any standards defined, including ISO/IEC 9126, most of these are static — none of these models really describe the relationship between phases in the product development cycle and appropriate usability measures at specific project milestone. We should note that any standard also gives relatively few guidelines about how to interpret scores from specific usability metrics. And specific to usability as a quality factor, it is worth to note that usability is that aspect of quality where the metrics have to be interpreted.

In this light when we look at popular Beta-Testing tools of today, we can notice that the Top Beta Testing tools leave the interpretation to the customer’s or end user’s discretion. This brings to our Number one challenge in Beta Testing — How to filter-out pure perception from the actual & valid issues and concerns?   As most of the issues are related to user-testing, split-testing, and front-end testing, there is no optimized single window solution that is smart enough to handle this in an effective way.  Real users in the real environment are unless empowered are handicapped to comprehend all the aspects of beta testing and react. Also, it’s all perspective and all of them cannot be validated with real data from some benchmark/standards.

The World Quality Report in 2015-16 Edition indicated that the expectations from the Beta testing is changing dramatically. It hinted that the customers are looking for more product insights through a reliable way to test quality, functionality along with the regular usability and user testing in real customer facing environment.

It’s not only the Beta Testing rather in the overall testing scenario, more user-demand is also getting impacted by the rising complexities and the challenges which is increasing due to accelerated changes in the technology, development and delivery mechanisms and approaches. The 2017-18 World Quality Report reports that the test environment and test data continue to be Achilles heel for QA and Testing along with the fact that the challenges with testing in agile development are increasing. There is now a demand for automation, mobility, and ubiquity along with smartness to be implemented in the software quality testing. Many believe that the analytics-based automation solutions would be the first step in transforming to smarter QA and smarter test automation

While this true for overall QA and testing, this is also true for Beta Testing, even when this testing, unlike the unit testing, system testing etc. deal with the functional aspect of the product.

Let’s see where we stand today as per this benchmark. If we explore popular beta testing solutions, we will get a big vacuum in the area where we try to benchmark user’s need for more functional aspects along with the usability and user testing aspects are mapped. Also, you can notice in the diagram that there is ample space to play around with the smart testing scenario with the use of cognitive, automation and machine learning.

(Note: Above figure shows my subjective analysis of the competitive scenario.)

Basically, we lack “Smartness” and proper “automation” in Beta Testing Solutions.

Apart from all these, there are some more challenges that we can notice if we start evaluating the user needs from the corresponding persona’s viewpoint. For example, even when assuming that the functional aspect is to be validated, the end-user or the customer may have an inability to recognize it. As the product -owner, customer or the end-user who are the “real users in a real environment”, are part of the user segment who may not be aware of the nuts and bolts of the technology involved in the development of the product they are testing to sign it off. It’s like the classic example of a customer who is about to buy a second-hand car and inspects the vehicle before making the payment. In most of the cases, he is paying the money without being able to recognize “What’s inside the bonnet!”. This is the ultimate use-case that advocates to “empower the customer”.

Now how to empower the end user or the customer? The tools should support that in a way so that the user can have his own peace of mind while validating the product. Unfortunately, many small tools who try to solve some of those little issues to empower the user (for example the Google Chrome extension that helps to analyze CSS and creating the report or an on-screen ruler that the user can use to check alignment etc.) are scattered. The ground reality is that there is no single-window extension/widgets based solution available. Also, not all widgets are connected. And those which are available, not all are comprehensible to the customer/end-user as almost all of them are either developer or tester centric. They are not meant for the customer without any special skills!

 

When we look at the automation solutions in testing as part of much Continous Integration (CI) and Continuous Delivery (CD), are engaged and effective in mostly “pre-beta” stage of SDLC. Also, they require specific skills to run them. With the focus on DevOps, in many cases, the CI-CD solutions are getting developed and integrated with the new age solutions looking at the rising complexities of technology stacks, languages, frameworks etc. But most of them are for the skilled dev or test specialists to use and execute them. And this is something that does not translate well when it comes to Beta testing where the end-user or the customer or the “real user in real environment” are involved.

Apart from all these even, assuming we can have all these automation features enabled in BETA it still points to another limitation in the existing solutions. It’s because the employment of automation brings in its own challenge of “information explosion” , where the end user needs to deal with the higher volume of data from automation and with so much information, the user will struggle to get a consolidated and meaningful insight of the specific product context.   So what we need to solve these challenge? Here is my view — We need smart, connected, single window beta testing solution with automation that can be comprehensible to the end-users in a real environment without the help of the geeks.

For sometime since a last few years, I have been exploring these aspects for the ideal Beta Testing solution and was working on the model and a proof of concept called “Beta Studio”, representing the ideal beta testing solution, which should have all these — Beta-Testing that utilizes data from all stages of SDLC and PLM along with the standards + specs and user testing data to provide more meaningful insights to the customer.  Test real application in real environment by the real users. Customer as well as end-user centric. Test soft aspects of the application — Usability, Accessibility, Cosmetic etc.  Smart enough to compare and analyze these soft aspects of the application against functional testing data.

Use machine-learning & cognitive to make the more meaningful recommendation and not just dump info about bugs and potential issues.

Here is an indicative vision of Beta Studio:

 

Mostly this vision of the ideal beta testing solution touches upon all the aspect we just discussed. It also touches upon all the interaction points of the different persona e.g. customer, end-user, developer, tester, product owner, project manager, support engineer etc. across the whole Product Life Cycle and utilizes automation along with the Machine Learning components such as Computer Vision (CV) and Natural Language Processing (NLP) to gather information that has to be processed by the cognitive aspect to generate the desired insights about the product and recommendations. During this process, the system will involve data from standards and specs along with the design benchmark generated from the inputs at the design phase of the SDLC, so that meaningful insights can be generated.

In order to achieve this vision being translated into reality, what is that we need. The following diagram hints exactly on the same:

Basically, the first step should involve creating the design benchmark from the information from the design stage, that can be used in comparing the product features against a metrics based on this design benchmark.

The second thing that matters should be automated and manual tracking of the product during runtime in real time and categorize and collate these data.  The third step involves creating features to support the user feedback cycle and user testing aspects (exploratory, split testing capabilities).

The fourth step would be to collect all standards and specifications on different aspects — e.g. Web Content Accessibility Guideline (WCAG) Section 508, Web Accessibility Initiative Specs ARIA, Design Principles, W3C Compliance, JS Standards, CSS Standards & Grids, Code Optimization Metrics Error codes & Specs, Device Specific Guidelines (e.g. Apple Human Interface Guideline) etc.

The fifth is about building the critical components such as Computer Vision and Natural Language Processing units which would process all the data collected in all these stages and generate the desired metrics and inferences.

The sixth step involves building the unit to generate the model to map the data and compare against the metrics.  The final or the seventh step is to build the cognitive unit that can compare the data and apply the correct models and metrics to carry out the filtering of the data and generate the insights which can be shared as actionable output to the end-user/customer.

While experimenting for BetaStudio, I have explored different aspects and built some bare bone POCs. For example, Specstra is a component that can help create Design benchmark from design files.

When I was exploring Specstra , that was trying to address the issues related to the Cosmetic aspect or visual look and feel. Typically when it comes to cosmetic issues, more than 30% or one-third issue are non-functional and mostly Cosmetic, there is no reliable solution that helps in benchmarking this kind of issues against some specific standards. At a minimum, one third of the issues found during the beta / UAT stages of testing are mostly cosmetic and alignment issues including category 3 and 4 types. And these happen mostly because the two personae – developer and designer involved have their own boundaries defined by a mythical fine line.

When a developer is in focus roughly 45% of them do not aware of all the design principles employed or the heuristics of UX to be employed. Similarly half of the designers are not aware of more than half of the evolving technological solutions about design.

And in mostly three fourth of the of the projects, we do not get detailed design specs to benchmark with. Detailing out a spec for design comes with a cost and skills. In more than two-thirds of the cases of development there is the absence of detailed design with specs. Wherever it exists many of the designs are not standardized, also most of them do not have clear and detailed specs. Also being design is carried out by different tools it is not always easy to have a centralized place where all the designs info is available for benchmarking.

To solve this Specstra comes handy as it is an Automation POC that is more like a cloud-based Visual Design Style Guide Generator from the third party design source files – this is a case where the user would like to continue using his existing Design tools like Photoshop/Sketch or Illustrator, PDF etc.

You can view the video of the demo here

 

https://youtu.be/_o4taIXCvck or read more here https://medium.com/design-ibm/specstra-experimenting-with-automation-in-design-industry-4641c0b4244d or here https://yourstory.com/read/71b0d89e20-specstra-experimenting-with-automation-in-design-industry

Similarly, the single window solution of tracking and be getting the real-time data on accessibility, visual design, CSS, JavaScript & Environment etc. from the product is explored in this POC. View a video on Beta Studio POC here https://youtu.be/kItqD5wc4_4.

 

I know reaching the goal of an ideal beta testing solution might need the effort and time and the concept will also evolve over time. But for sure the journey has started for all of us to connect and explore how to make it a reality.

Feel free to ping me in the comment section of this article.

To explore the open-source project of BetaStudio poc , follow the link here –https://github.com/betaStudio-online (will be uploading all the code to the repos in these in coming times. )

How I Created a Software That In-turn Helped Me Creating My Graphic Book

It’s the story of Rangoli , my own custom developed cloud based image editor software that helped in churning-out the print ready images to help in creating a graphic book with specific effects to set the desired nostalgic tone.

If I today look back in time, I find many memories from Rourkela, a small township around India’s first public sector steel plant. Like any other Rourkelite, I have been a true enthusiast about my town. This passion led me to spend some time in last few years to collects smaller yet evocative details of events that shaped the place and the life within it. Then a time came when I gave it a serious thought to give them a shape of a book. Last year I published the book as titled Rourkela – The Illustrated Journey Into The Life Of The City 

As the book was supposed to be a graphic novel, there were multiple challenges I had. The first and foremost of them was getting the images/photograph of the town across different times in history. Being a small town it was really difficult task as not much of the facts and history of the place was recorded from different aspects of life. before the Rourkela Steel Plant was built in 1950’s, the place was least known tribal area with in the dense forest across the hills. Even though a high level details I had collected from secondary research, still the details were not enough to come up with a photographic book with truthful and accurate particulars. The problem with photographs is that they are too real – there is a little room available for imagination when you see a bright sharp hi definition photograph. The less details are in photo including color, there is more to imagine , and no doubt that’s why a painting with less realism is always effective in igniting emotion in viewer than the same subject in photograph.

https://www.linkedin.com/pulse/api/edit/embed?embed=%257B%2522type%2522%253A%2522video%2522%252C%2522title%2522%253A%257B%2522localized%2522%253A%257B%2522en_US%2522%253A%2522RANGOLI%253ACreative%2520Studio%2520-%2520Samir%2527s%2520Experiment%2520in%2520Image%2520Processing%2520over%2520Cloud%2522%257D%257D%252C%2522description%2522%253A%257B%2522localized%2522%253A%257B%2522en_US%2522%253A%2522Rangoli%2520is%2520a%2520fully%2520automated%2520cloud%2520based%2520creative%2520studio%2520app%252C%2520that%2520helps%2520in%2520converting%2520images%2520into%2520complex%2520sketches%2520and%2520artistic%2520outputs%2520that%2520can%2520be%2520used%2520for…%2522%257D%257D%252C%2522author%2522%253A%257B%2522name%2522%253A%2522Samir%2520Dash%2522%257D%252C%2522provider%2522%253A%257B%2522name%2522%253A%2522YouTube%2522%252C%2522display%2522%253A%2522YouTube%2522%252C%2522url%2522%253A%2522https%253A%252F%252Fwww.youtube.com%252F%2522%257D%252C%2522request%2522%253A%257B%2522originalUrl%2522%253A%2522https%253A%252F%252Fwww.youtube.com%252Fwatch%253Fv%253DGY27CzxwPp8%2522%252C%2522finalUrl%2522%253A%2522https%253A%252F%252Fwww.youtube.com%252Fwatch%253Fv%253DGY27CzxwPp8%2522%257D%252C%2522images%2522%253A%255B%257B%2522url%2522%253A%2522https%253A%252F%252Fi.ytimg.com%252Fvi%252FGY27CzxwPp8%252Fhqdefault.jpg%2522%252C%2522width%2522%253A480%252C%2522height%2522%253A360%257D%255D%252C%2522data%2522%253A%257B%2522com.linkedin.treasury.Video%2522%253A%257B%2522html%2522%253A%2522%253Ciframe%2520scrolling%253D%255C%2522no%255C%2522%2520allowfullscreen%2520src%253D%255C%2522%252F%252Fmedia.licdn.com%252Fembeds%252Fmedia.html%253Fsrc%253Dhttps%25253A%25252F%25252Fwww.youtube.com%25252Fembed%25252FGY27CzxwPp8%25253Ffeature%25253Doembed%2526amp%253Burl%253Dhttps%25253A%25252F%25252Fwww.youtube.com%25252Fwatch%25253Fv%25253DGY27CzxwPp8%252526feature%25253Dyoutu.be%2526amp%253Btype%253Dtext%25252Fhtml%2526amp%253Bschema%253Dyoutube%255C%2522%2520width%253D%255C%2522480%255C%2522%2520frameborder%253D%255C%25220%255C%2522%2520class%253D%255C%2522embedly-embed%255C%2522%2520height%253D%255C%2522270%255C%2522%253E%253C%252Fiframe%253E%2522%252C%2522width%2522%253A480%252C%2522height%2522%253A270%257D%257D%257D&signature=AQYbS5FyMfkBVs5b6NHV0b3Oc7aY

(FIG: The images in the published book – the line textured engraving effect gives the feeling of vintage nostalgia.)

As the book subject was history of the town with reference to different location within and specially about the town’s inception in 1950’s, and before, I thought it would be great to use illustration type graphics to match the old times, specially 50’s and 60’s of the town. In addition to that the challenge was that as it was a place, about which very less photographs along with recorded information was available, it was difficult to come up with a graphical history of the places through photographs. Secondly due to unavailability of details of life style and location description of the area, (as Rourkela was mostly unknown remote hilly area filled with jungle and aboriginal tribal before the steel plant came up in 50’s just after a few year of India’s Independence ), leaving something to imagination of the readers in images is ideal to evoke certain emotions.

When I started looking for a theme of the graphic book on history of a location, I explored many font types, graphic styles along with sketch patterns. I wanted the book to bring back nostalgia about the past that gone by, to remind the readers of the days gone by which no more exists. So natural tendency was to select vintage designs mostly popular in the periodicals, books and magazines printed using older print approach like wood-cut , linograph and engraves and the kind, when digital print didn’t exist which ever maintain the crispness of our printing methods today and had the printing imperfections. So I selected the wood-cut, old style text and textured background of the background images which help get the reader he feeling of vintage nostalgia.

The next step was to look for options to produce such an effect. After a search I noticed there are some plugins to Photoshop and other similar photo editors which provide the similar effects. But as I am more biased towards open source and used GIMP most of the time for my graphical needs, I wanted a good plugin that would provide the desired effect . There were some yet they didn’t match the exact way I wanted to represent the images. I wanted something to closely match the childhood local magazines that were printed and were more crude looking printouts. So the one of the best choice was to rather develop a program to quickly produce the exact effect I wanted to invoke same feeling. Initially I thought of learning to develop a plugin for GIMP, but that included additional work to learn the new language and the methods to build the plugin. Yet I did not want to depend on simple actions. Also I was not interested in depending on a commercial software and stick to it and was also not sure how long it would take me to learn and there by come-up with the solution that will in turn will help me complete my book project. I was stuck at a cross road, where the other option is to look around and find an approach that would be easier for me to come up with a software solution that will involve less work. I realized, I knew a decent level of PHP and some open source image processing libraries. In my earlier days of my career as a developer, I had played a lot with such libraries which used to run over shell scripts and via PHP through Execs. So Decided to try out this approch and decided will build my own Image Editor application that will allow to upload any image and convert that to the effect I desired. Thus my pet project Rangoli came into being to help me out to finish my graphic book project.

After spending two months over weekends, quickly I managed to build a working version with a feature to convert my images into the desired effect. As I used PHP, I was able to host it locally and use it across different laptops I use at home via the wifi , without the need to install anything on the system I was working with my book project. Later I added a few more variations of the effect and build a template that can be used to add more effects like plugins into ‘Rangoli’. One such addition was to remove either the white or black from the image and make it semi transparent (the same effect you get in Photoshop by turning the blending mode to ‘Multiply’).

(FIG: Rangoli Interface showing the list of effects available and the preview in center pane. Multiple effects can be queued and batch processed.)

Later added the feature to process multiple effects one after another based on the queue — more like a batch process but through the GUI and by following human friendly language than the geek’s favorite commands. These helped me build a system that is scalable and cross platform by the time I finished the book.

(FIG: Rangoli user-interface showing the rendered vector image with transparency, ready to be used in the book.)

Using this then I started creating visuals for my book. I merged multiple public domain images and some photographs I took some time back across the town, to create desired frame which then I processed in Rangoli to generate print ready vector that with old engraved vintage type image.

(FIG: From Left to right, different stages the source images were merged and then fed into Rangoli to get the old print type shown in right.)

The one more good thing happened – in my book I was able to provide dramatic scenes from past combining some modern day photographs and processing them through Rangoli.

(FIG: Blurring the realism – Left images are the original ones processed, where are the right one are the finally processed outputs from Rangoli.)

Finally I was able to complete the book that was referred as “Mini India’ Rourkela coming alive through flickers of images”. Though technology helped me in a greater way by empowering me to meet my goal which otherwise would have been impossible for me, I learned a new trick — sometimes, we need to spend time in building components that will help us in long run . In such cases even if the immediate or direct benefit may not be in sight, still they may act as the foundation stone to the bigger thing we desire to achieve.

You can get the book from here: http://amzn.in/9pobnWq 

https://www.linkedin.com/pulse/api/edit/embed?embed=%257B%2522type%2522%253A%2522video%2522%252C%2522title%2522%253A%257B%2522localized%2522%253A%257B%2522en_US%2522%253A%2522Experiment%2520on%2520the%2520Book%2520Form%2520-%2520History-cum-Travel%2520in%2520Comic%2520Book%2520Format%2520%2528Book%2520on%2520Rourkela%2529%2522%257D%257D%252C%2522description%2522%253A%257B%2522localized%2522%253A%257B%2522en_US%2522%253A%2522Rourkela%2520-%2520The%2520Illustrated%2520Journey%2520Into%2520The%2520Life%2520Of%2520The%2520City%2520Around%2520India%2527s%2520First%2520Public%2520Sector%2520Steel%2520Plant%2520Author%253A%2520Samir%2520Dash%252C%2520Sangeeta%2520Dash%2520Format%253A%2520Paperba…%2522%257D%257D%252C%2522author%2522%253A%257B%2522name%2522%253A%2522Illustrated%2520Type%2522%257D%252C%2522provider%2522%253A%257B%2522name%2522%253A%2522YouTube%2522%252C%2522display%2522%253A%2522YouTube%2522%252C%2522url%2522%253A%2522https%253A%252F%252Fwww.youtube.com%252F%2522%257D%252C%2522request%2522%253A%257B%2522originalUrl%2522%253A%2522https%253A%252F%252Fwww.youtube.com%252Fwatch%253Fv%253Dzs34MxEXTmo%2522%252C%2522finalUrl%2522%253A%2522https%253A%252F%252Fwww.youtube.com%252Fwatch%253Fv%253Dzs34MxEXTmo%2522%257D%252C%2522images%2522%253A%255B%257B%2522url%2522%253A%2522https%253A%252F%252Fi.ytimg.com%252Fvi%252Fzs34MxEXTmo%252Fhqdefault.jpg%2522%252C%2522width%2522%253A480%252C%2522height%2522%253A360%257D%255D%252C%2522data%2522%253A%257B%2522com.linkedin.treasury.Video%2522%253A%257B%2522html%2522%253A%2522%253Ciframe%2520scrolling%253D%255C%2522no%255C%2522%2520allowfullscreen%2520src%253D%255C%2522%252F%252Fmedia.licdn.com%252Fembeds%252Fmedia.html%253Fsrc%253Dhttps%25253A%25252F%25252Fwww.youtube.com%25252Fembed%25252Fzs34MxEXTmo%25253Ffeature%25253Doembed%2526amp%253Burl%253Dhttps%25253A%25252F%25252Fwww.youtube.com%25252Fwatch%25253Fv%25253Dzs34MxEXTmo%252526feature%25253Dyoutu.be%2526amp%253Btype%253Dtext%25252Fhtml%2526amp%253Bschema%253Dyoutube%255C%2522%2520width%253D%255C%2522480%255C%2522%2520frameborder%253D%255C%25220%255C%2522%2520class%253D%255C%2522embedly-embed%255C%2522%2520height%253D%255C%2522270%255C%2522%253E%253C%252Fiframe%253E%2522%252C%2522width%2522%253A480%252C%2522height%2522%253A270%257D%257D%257D&signature=AQGLpYWXM5trMpF0f4NyvZxr60f_

Rourkela – The Illustrated Journey Into The Life Of The City Around India’s First Public Sector Steel Plant

A new type of history book about a city ..600+ illustrations, 270 pages , about India’s first public sector steel plant and a city around it… legends, facts, figures..about tribals, their life, about the British Raj and post modern Indian scenario..about how the steel industry came up in the remote area and how the city got into Narendra Modi’s smart city list..

A new type of history book about a city ..600+ illustrations, 270 pages , about India's first public sector steel plant and a city around it... legends, facts, figures..about tribals, their life, about the British Raj and post modern Indian scenario..about how the steel industry came up in the remote area and how the city got into Narendra Modi's smart city list..

 

Completely illustrated narrative about Rourkela, a city that become one of the iconic industrialization urban symbol in post independent India. A remote village of the ‘Roulia’ tribe, surrounded by dense forests and hills amidst India’s one of the mineral rich valleys, got selected by the makers of modern India to host India’s first public holding Steel and Iron company Hindustan Steel Limited. This story is the the journey of becoming one of the founding stones of modern industrialization of India. “History of a less travelled yet one of the cult cities of modern Indian town retold disguised as a compelling and gripping story through pictures” Explore the fine details about the place, it’s aboriginal, the migrant population, the culture and the impact of urbanization in social life. An unique experimental book of it’s own kind.

GET YOUR PAPERBACK https://amzn.com/1539083187

GET YOUR PAPERBACK https://amzn.com/1539083187

 

MakingSense: Reimagining the Next-generation Retails and e-Commerce Analytics platform

journey-consumerbenefits

 

 

In today’s ever changing world if we need to reimagine the next generation analytics platform for retail and e-commerce market, what it will look like? Well I gave it a go . Following is a conceptual framework (I call it  “MakingSense”) and a business case for an IoT based real time analytics framework for retail and FMCG market. The following post is presented as a real life business case:

 

 

 

 

Overview:

MakingSense” is IoT based market analytics platform to connect all goods and products (specially non-digital goods) that behave as fast moving goods to the cloud-analytics to get real-time market insights to make the required course correction for the market strategy and business decisions for the product manufacturers and retail chains. This enables a direct feedback model between the consumers with the producers and sellers.

 

The problem it solves:

As per current market trends, even high-tech goods like mobiles, digital accessories are behaving like FMCG in market. Rapid change is evident in consumer behaviour due to influence from technology, economy and changing buying power of the consumer . Speedy ‘go-to-market’ approach in the market from players in the market has increased the competition. Many local and niche competitors are giving tough challenges to bigger players in all segments, specially in emerging markets. For globl players the typical market strategy is not working in expected way. Traditional approach of market insights collection is not sufficient to apply the necessary check and balance for market plans in real time.

 

The 4 core needs that Making Sense will address are:

1.The manufacturers need market insights in real time

2.The consumer behaviour towards tech-goods is also needs to be tracked in real time to ensure how close they are behaving to the FMCG market behaviour.

3.In retail and non-tech sector the real time insights are needed for goods that are not digitally connected to analytics eco-system

4.Need to look beyond the traditional field immersions, surveys to get micro-insights for course corrections in strategy.

 

The solution and the business model:

The “MakingSense” platform will help product manufactures and retailers in gathering real time customer insights even for non-digital goods and helps adjust the customer retention dynamics . In retail and non-tech sector the real time insights are needed for goods that are not digitally connected to analytics eco-system. Need to look beyond the traditional field immersions, surveys to get micro-insights for course corrections in strategy.

The platform has self sustainable business model that will make it grow though benefiting the product manufacturers, retailers and the consumers. The final envisioned eco-system will have a big-data enabled management module in cloud, a super easy to use dashboard system for product manufacturers, retailers and consumers and mobile apps and easy integration public APIs along with one SMS enabled gateway.
The producers and sellers can register their products to generate specific code to their products category and if required can use the APIs to map their existing bar-code systems. The normal consumer can register themselves to generate the reward points and to be used directly in the registered retail chains or can redeem for some gifts from their dashboard itself.

The eco-system will allow the product companies and sellers to get real time analytics through creating data points directly.

 

 

Triple advantage benefits for consumers:
The incentivise/rewarding consumers for their feedback is what will make it more successful.
Whether the product the consumer gives feedback on is purchased from the registered retailer or not, he is definitely getting the reward points or freebies from the site.
If he purchases the product from the registered retailers, then he is getting additional discounts or reward points.
On top of it if the product manufacturer registers, then the customer is getting more discounts!

It’s a triple advantage for the customer.

Now, this is a new strategy where the customer is prompted to buy the product from specific manufacturer, from a specific retailers toget advantage of this.
While the whole aim is to get feedback and analytics running, this model also induces a new competition on product manufacturers to provide discounts to bring down the final competitive price to retain customers at the same time the customer is also getting benefitted.

This model is disruptive in nature where every one is getting benefited :

Manufacturer and Retailers – reduction in market research spending , getting real time-analytics — the mood of the segment- customer retention strategy formulation , attract customer to their outlets and
Consumer — reduction in home budget, get incentive, rewards for their feedback.

 

 

 

::Idea::

 

The “MakingSense” platform will help product manufactures and retailers in gathering real time customer insights in real time even for non-digital goods. In retail and non-tech sector the real time insights are needed for goods that are not digitally connected to analytics eco-system. Need to look beyond the traditional field immersions, surveys to get micro-insights for course corrections in strategy.

The platform has self sustainable business model that will make it grow though benefiting the product manufacturers, retailers and the consumers. The final envisioned eco-system will have a big-data enabled management module in cloud, a super easy to use dashboard system for product manufacturers, retailers and consumers and mobile apps and easy integration public APIs along with one SMS enabled gateway.

The producers and sellers can register their products to generate specific code to their products category and if required can use the APIs to map their existing bar-code systems. The normal consumer can register themselves to generate the reward points and to be used directly in the registered retail chains or can redeem for some gifts from their dashboard itself.

The eco-system will allow the product companies and sellers to get real time analytics through creating data points directly

:: Architecture:

The idea is about building an eco-system in multiple-phases that will have three components:

1. “MakingSense SmartCloud” — Cloud based server to store the data related to the consumers and host the analytic platform. This will have the following major components :
i. BigData analytic-engine that can do the necessary data mining to understand trends and formulate recommendations .

ii. Open REST APIs providing easy way to integrate third-party systems such as retail-management systems, third-party analytic and business process tools/apps.

iii. user management modules with different levels of access to different roles.

iv. Reward points management and coupon code management system.

v. Payment gateway and subscription and vendor management.

2.”MakingSense Portal” — Web-based portal/ thin-client solution that will allow consumers and product sellers/retailers who can register and access their respective dashboards

3. “Making-Sense client” — This is primarily mobile/device client and consumer facing service gateways (and optionally hardware) that can be used by the consumers to submit their feedback.
In the multi-phased development roadmap, initially the mobile apps will be primary representative of this section. Later phases will introduce SMS enabled gateways, custom “MakingSense” hardware, which will be cheap yet provide easier way to share data from the consumer.

 

:: User Journeys:

For Sellers (Retailers/Producers)-

1. gets account registered at ‘MakingSense Portal’.
2. get API if to connect to their card scanners /billing machines/users db/inventory/product catalog
3. gets products mapped to “Reward points”/discounts/freebies
4. product manufacture can offer discounts for their product using the API by registring their product

5.product manufacture can register their product to get insight for their product across globe
6.retailers get insight for their retails chains –anything sold though their system
7.retailers can buy insights (not customer details ) for other regions/ segments
8. product manufacturers can buy insights (not customer details) for competing brands and similar products

For Consumer –

1. Registers at the Portal — if he is from a retailer’s database, he can map his account to this system.
2. Connection to his SNS account (facebook) is encouraged (with some additional reward for it)
2. downloads free “makingsense” mobile app, and starts using
3. scan the barcode of any product he purchased and rates the product.
4. For each feedback on different (at least different batch of same product with in a specific time period range) the products, gets “reward points” or discounts codes or freebies coupon codes.
5. If retailers/product manufacturer has sponsored rewards, based on accumulated points, he can redeem them at their store. Else these can be redeemed at the “makingSense” dashboard at the portal.

:: Benefit:

For Sellers (Retailers/Producers)-

emerging market is the next potential
even high tech/high end goods are behaving like FMCG goods…
micro -insights are required to plan the market startegy adjustment
conventional type of large scale survey’s are not going to help much due to high cost and field immersion efforts and time.. — go-to-market is accelerating so ..time has value … micromax makes a phone in 70 days

So new age trend is required to gather data in real time ..to connect goods that are not even digital , we need those data
IoT will help in rapidly accessing this.

They get the following insight from the solution:

customer’s insight
————
who bought
how many times bought
which part of the year bought the most
consumer’s insight
—————————
liked? great – good – bad ?
what else he likes in the same product line ?
what similar product he uses?
what similar product he likes most ? what brands?
collective consumer insights
—————————-
how many such buyers are in the region who are potential buyer?
how is collective preference?

predictive market forecast
—————————-
in which part of the year the product consumption is going to increase — manufacture more and ensure smooth shelf-space management
who are competitor brands
how a product is behaving in a segment?
value curve?
what should be the status?

if connects to his SNS account/FB/retail shopers card — then u get location, age, gender, type etc. — new gold mine where every one will want to invest.

For Consumer –

1. Consumer is rewarded for any feedback he shares for any product he uses.
2. Apart from regular discounts, reward points the customer can get these additional discounts in purchase/freebies which can bring customer delight leading to more involvement and customer engagement (so no matter if consumer does not buy from registered retailers or products.)

 

 

 

 

 

:: Business model::

Business model is mostly through subscription based to access competitor analytics
Along with it the access to premium data and value added services like (customizable report, goal alignment, market strategy etc. ) can be a major source of revenue .

retailers get 100% discounts to access their data — all real time
retailers get 20-30% discount in viewing their competitor’s data in the same region or segment

retailers not listed in the program to have to pay full to get data for a segment
retailers not listed in the program can not view their data

consumer gets 2% bonus discounts or points to submit the feedback on every item he uses

 

 

:: Market Size::

As per ESOMAR Global Market Research conducted in 2011:

Global Spending on Market Research is 32 Billion USD.
Out of this Emerging Market share is 24% == 8 Billion USD
Out of this only Asia Pacific spending is == 5 Billion USD.

India & China are major share holders of 5 Billion USD
India == 40% of 5 Billion USD = 2 Billion USD

Based this 1st year
target in five 1st tier cities.
assuming 30% investment is done in these 5 cities == 0.6 Billion USD
assuming we get 30% of this share in 1st year == 0.2 Billion USD

That results in 100 Cr INR Revenue in 1st year .

 

 

 

:: Potential competitors & Competitive advantage of the idea::


Amazon Dash
Dash is a product by Amazon that allows to facilitate the consumer to order new products from Amazon store

 

 

Dash:

Hardware based + amazon portal is available for consumer to buy
Only limited to Amamzon portal
No-whitelabelled system — Amamzon uses it for it’s own usage.
It’s is NOT a feedback based model, the bigdata only shows which segment is purchasing which product.

 

Making Sense:

Special marketing-insight platform – unique and first of it’s kind.
Specially designed to handle multiple vendors, retailers and consumers along with reward points/incentive management model .
Unique analytics with predictive strategy formation
works across cross platform, outlets, cross multi-channecommercialal platforms both counter based or online.

 

SWOT  Analysis

Strength: 

Cross platform – mobile, tablet, PC, kosk, custom hardware
works across cross platform, outlets, cross multi-channel commerceial platforms both counter based or online.
Can appeal to consumers, retailer, manufacturers

Can be scaled from FMCG to insurance, banking/finance sectors.
Weakness:
New concept, new to the market — disruptive business model for market research where customers are incentivised for their feedback directly.
Requires fund to maintain the incentives/ rewards for the end-consumers.
Large scale imkplementation can bring meaningful results??????
Opportunities:
New unique business model.
Regional market is drib\ven by fragmented retail / distribution channels
Specially FMCG market is highly un-organised
Penetration of single super markets, and online selling is low.
Specially in India the coverage of super markets (Big Baazar, )
Market insights
Threats:
Dash making it’s platform focused on marketing research
Marketing research companies replicating this model– alternative models
Retail chains making their own platform — will get limited view only only their customers..still they need to spend more in their marketing agencies.

 

 

:: Why it’s a killer Idea? ::

The incentivise/rewarding consumers for their feedback is what will make it more successful.
Whether the product the consumer gives feedback on is purchased from the registered retailer or not, he is definitely getting the reward points or freebies from the site.
If he purchases the product from the registered retailers, then he is getting additional discounts or reward points.
On top of it if the product manufacturer registers, then the customer is getting more discounts!

It’s a tripple advantage for the customer.

Now, this is a new strategy where the customer is prompted to buy the product from specific manufacturer, from a specific retailers toget advantage of this.
While the whole aim is to get feedback and analytics running, this model also induces a new competition on product manufacturers to provide discounts to bring down the final competitive price to retain customers at the same time the customer is also getting benefitted.

This model is disruptive in nature where every one is getting benefited :

Manufacturer and Retailers – reduction in market research spending , gettingf realtime analytics — the mood of the segment- customer retaintion strategy formulation , attaract customer to their outlets and
Consumer — reduction in home budghet, get incentive, rewards for their feedback.

 

 

 

As per Tim Ambler of London Business School, “Marketing Productivity” is measured through the following 5 ponts :

1. routinely research consumer beavior?

2. routinely report research with financial matrics?

3. compare results with previously forecasted in business plans

4. compare with level achieved by your competitor using the same indicators?

5. adjust short term performance?

 

All of these are taken care in the  blue print of “MakingSense”

 

 

 

 

 

 

 

Indoor Mapping in Consumer or Retail Vertical and it’s impact on UX

Mapping and localization for indoor mapping is gaining momentum in consumer verticals of IT and software services industry to propose new age technological solutions and process re-engineering services that helps in providing value added features to the consumers of the verticals. Also the consumer data mining and data analytics are pushing new dimensions with the indoor mapping technologies to provide new insights into the consumer and end-users’ psyche. This ultimately opening doors to provide better and delightful user experience for the user during his shopping experiences.

 

Technology Used for Indoor Maps

 

Despite the fact that the location determination of mobile users within a building has attracted much attention lately due to its many applications in mobile networking including network intrusion detection problems, it is challenging due to the complexities of the indoor radio propagation characteristics exacerbated by the mobility of the user. Global navigation satellite systems (GPS or GNSS, which act as the benchmark for the standard Map related applications development, are generally not suitable to establish indoor locations, since microwaves will be attenuated and scattered by roofs, walls and other objects. Due to the signal attenuation caused by construction materials, the satellite based Global Positioning System (GPS) loses significant power indoors affecting the required coverage for receivers by at least for satellites. In addition to this, the multiple reflections at surfaces cause multi-path propagation serving for uncontrollable errors. So the most popular among the technologies that are employed for indoor mapping scenario is the wireless technologies like Wifi and RFID.

In Radio-Frequency identification (RFID) systems, the simple concept of location indexing and presence reporting for tagged objects are used, that only acts as the object identification. Typically RFIDs do not report the signal strengths and various distances of single tags or of a pulk of tags and do not renew any before known location coordinates of the sensor or current location of any tags. Operability of such approaches requires some narrow passage to prevent from passing by out of range. In Grid concepts, a dense network of low-range receivers may be arranged, e.g. in a grid pattern for economy, throughout the space being observed. Due to the low range, a tagged entity will be identified by only a few close, networked receivers. An identified tag must be within range of the identifying reader, allowing a rough approximation of the tag location. Advanced systems combine visual coverage with a camera grid with the wireless coverage for the rough location.

 

The use enhanced Wi-Fi infrastructure to provide location information actually provides the missing piece that only RFID can not provide. WiFi infrastructure help in establishing more accurate and stable landmarks, which serve to anchor the various partial trajectories. This approach uses Received signal strength indication (RSSI) – that is a measurement of the power level received by sensor. Because radio waves propagate according to the inverse-square law, distance can be approximated based on the relationship between transmitted and received signal strength (the transmission strength is a constant based on the equipment being used), as long as no other errors contribute to faulty results.

 

Once the user and/or the tracking objects are located and tracked for their movement, the resulting data is mapped to the pre-built indoor location map to provide meaningful observations on the user’s location in particular section of indoor space and based on this the shopping experience of the user can be enhanced.

 

Indoor Maps in Consumer or Retail Verticals

During the last few decades, research on localization for exploration and navigation in indoor environments has made significant progress. However this technology was not accessible to the consumers till Google declared “indoor maps” as the future of consumer facing verticals, which successful attempts in utilizing this technology in shopping malls, museum and related public places where the real-time user analytics based on his location inside the shop helped formulating a set of customized offering to the user to make his experience easier and delightful.

IKEA, one of the world’s leading home furnishings company, uses Google indoor maps for improving customer’s experience in navigating the stores that are typically “typically a two level building that ranges in size from 200,000 sq ft to 450,000 sq ft–the average size is approximately 320,000 sq ft” and which typically “can work against” the “IKEA’s goal is to make the customer feel comfortable and in control of their shopping experience” — “People can have a hard time navigating the store. There have been stories of people saying that they feel like we are are purposely keeping them in.We want to make their shopping experience as easy as possible” (Google).

In a typical customer’s experience in a large sized mall, or shopping store can be frustrating, when he “want the option to quickly find their way to a particular product or throughout the store”(Ibidem,1)and this is mostly the consumer sees as the product he “needs”. Whereas the shopper or the store owner’s intention in most cases is to “encourage customers to find items they didn’t know they needed” – which is in fact conflicting with the thought line of the customer that is more inclined towards the self-gratification through the identification of items of his need.

 

 

The common set of expectations that lies among the conflicts of interests between the shop/store owner and the shopper provides the foundation that helps sustaining the user experience of the shopper in such an eco-system. The common set of expectations mostly revolve around the concepts of getting (for shopper)and providing (for shop-owner)the best possible experience. The common mission when equipped with the technology, such as indoor maps, sets the momentum of better usability and at the same time offers avenues for more cash flow for the store owner.

Most of the mall or stores which have implemented indoor mapping technology have been profitable by capitalizing “on the growing population of smartphone users” who can use the technology through their handsets. As of March 2012, over 106 million people in the U.S. owned a smartphone with Apple and Google having market share of 30% and 51% respectively — which shows that a significant mass of the consumers are also depending on mobility as a medium to consume the technology aided services. This fact is itself acting as a catalyst to propel the usage of indoor maps in consumer sector. (comScore, 2012).

 

Keeping the user in-touch during the whole experience

 

One of the successful features of the indoor mapping eco-system is to keep the user informed at every step of his experience and maintain a communication thread between the user and the system. A sample flow is shown below where the two way communication is illustrated.

 

 

The illustration above highlights how a simple two way communication is established between the user (through his app on his mobile) and the indoor mapping backend running and performs the analysis of user location data to execute productive actions that meets the user goals and helps improve the user’s over shopping experience in the store.

(c) 2013-14, Samir Dash

UX Simplified: Models & Methodologies: Digital Edition [Kindle Edition] ISBN: 978-1-3115-9110-4

My  recent title is available on Kindle for download. This book covers basic models and methodologies that are revolved around User Experience (UX). The discussed topics include User Experience, Information Architecture, User Interface, Usability models, User Centered Design (UCD), User Centered Software Design (UCSD), different Software Lifecycles (SDLC) and how usability models fit into SDLC models.

The details of the book are as follows:

UX Simplified: Models & Methodologies: Digital Edition
by Samir Dash
ISBN: 978-1-3115-9110-4
ASIN: B00LPQ22O0

Kindle Price (US$):$1.87
Kindle Price (INR):Rs. 119.00 includes free international wireless delivery via Amazon Whispernet

http://www.amazon.com/dp/B00LPQ22O0/ref=r_soa_w_d

 

 

UX Simplified: Models & Methodologies: Digital Edition [Kindle Edition] ISBN: 978-1-3115-9110-4
UX Simplified: Models & Methodologies: Digital Edition [Kindle Edition] ISBN: 978-1-3115-9110-4
Major topics included in this book are :

• Why “UX: Simplified”?
o The Diverse Disciplines: The ABCs of UX
o User Experience(UX)
o Information Architecture(IA)
o Interaction Design (IxD)
o User Interface Design (UI)
• Usability and Mental Models: Foundations of UX
o What is Usability?
o System Models
o What is a “Mental Model” exactly?
o Most-likely Mental Model
o Conceptual Model
o Challenges in Usability Measurement and Metrics
o A List of Factors for Generic and Consolidated Usability Model
o Heuristics:Measuring Usability
• Engineering and Design Processes: Usability and User Centric Approach
o Usability Engineering
o User-Centered Systems Design (UCSD)
o Usability Design
o User-Centered Design (UCD)
o Don’t get Confused: UCD vs UCSD
o UCD Models and Process
• Software Development Life Cycle (SDLC): Where and How User Experience Models fit in?
o Software Development Life Cycle (SDLC)
o Waterfall model
o Spiral model
o Iterative Development Model
o Agile development
o Challenges in UX Integration to Different SDLC Models
o Usability Designing Process
o How Usability Design Process Fits in Different Phases of SDLC?
o How UX Fits in Different Models of SDLC?
o Challenges with Agile model of SDLC to implement UX
o Lean UX and Agile Model
• Agile in Usability Design:Without Reference to SDLC
o Usability Designing Process
• Lean UX: Another Agile UX?
o The Beauty of Lean UX: Everything is familiar
o Foundation Stones of Lean UX:
o Lean Startup method: The concept of “Build-Measure-Learn”
o Minimum Viable Product (MVP) – Prototyping at it’s best in Lean Startup Method
o Principles of Lean UX

  • File Size: 1435 KB
  • Print Length: 86 pages
  • Simultaneous Device Usage: Unlimited
  • Sold by: Amazon Digital Services, Inc.
  • Language: English
  • ASIN: B00LPQ22O0