When can you expect my next blog post?

Just in case you're one of those wondering whats with the series of posts in my blog over the past few days, yes I did make 4 posts in 3 days. Now, let me help you understand why and also possibly answer the question in this posts' title, by digging into some data in the background.

Since I resumed blogging early last year, I've posted 90 articles here. Lets first look at the rhythm of posting, something that I've written several time earlier about, and have been striving extra-hard to maintain. The posting pattern over the nearly 2-year period is as follows:

From the above its clear that I've managed to maintain some consistency over the months; an average of 4.04 posts per month. However, whats not obvious here is the posting pattern within the month. To understand potential effect of my self-imposed monthly deadline, we'll have to look at when the posts are made within each month.

I've split each month into 3 periods: 1-10th, 11-20th and 21st until end of the month. When the monthly aggregation is broken down into these periods, some patterns start emerging. I've made a small correction for the bulk-publishing of my back-packing diary, which incidentally was posted in the middle of the month (17th May '15), after weeks of writing. I've changed the value of '17 posts' on this date to an above-average number of '2 posts', as an approximation.

The below table is coloured to show which of the 3 periods within a month have most posts, over the last 2 years. Its obvious that I've hardly made any posts in the first 10 days of any month (red shaded cells below), while the last 10 days are fertile periods, showing up in green. Most of the posts are generally made in the last 10 days of a month, at times spilling over into the last few days within this cycle.

What this also means is that roughly two-thirds of all posts are made a few days before the deadline! Old habits die hard, so guess I'll have to change the deadline to a weekly one as opposed to monthly. Perhaps, that could help spread out the posts through the month.

Hopefully my next post would be earlier than the 30th of December, though the above analysis strongly suggests that as the possible answer!

Making most of your Best-before-Date

For a moment picture yourself living in this world about 50 years ago, in an age where automobiles were relatively fewer and it was a real luxury to have one in the neighbourhood. Assume you didn't own a car already, and were given one on lease, for a limited period of 30 days along with free fuel. Suppose you were given complete freedom to use it in any way you deemed right, what would you do?

You would use this (relatively rare) mode of transportation to get all your stuff done: for work, personal needs and moving things around. You would use it to the fullest and perhaps flaunt it too. You might also run a few errands for friends and neighbours. You would consider making the best use of this rare commodity available only for a limited period, just so that the benefits stay long after the lease period.

• Would you use your car for just one purpose (only commuting to work) and let it stay idle otherwise?
• Wouldn't you plan that elusive long-drive on a weekend? Plan a vacation driving to that exotic locale, with friends and/or family?
• Wouldn't you do the bare minimum to keep the vehicle in a running state by refilling fuel, checking tyre pressure and doing the needed maintenance? The last thing you'd want is the vehicle to break down and be out of service for 2 of the 30 days.

Now why do we handle our lives any differently? Coming to think of it, there are striking similarities with the above analogy.

• We have limited time in this life (a 'lease' in years as opposed to days for the car). 
• Each person has incredible talents and unique interests, which often get neglected by narrow-minded pursuit of one or a few things (bogged down with work / too internally focused to look outside / not taking time to appreciate and contribute to the good things in this world). 
• And, its a criminal negligence to neglect our body without the needed 'maintenance' that is essential to ensure good health. The quote by Jim Rohn nails it - "Take care of your body, its the only place you have to live".

Pic source

Monetising the demonetisation decision: The Paytm story

The past few weeks have had non-stop coverage of the demonetisation of currency and demonisation of mistry. The jury is still out on both these controversial decisions. Particularly, the demonetisation drive has split public opinion like never before. If I look at my close circle of friends, I've never seen them split to take up two diametrically opposite sides of an issue like this ever before - one camp owning up the decision and actively preaching its benefits, while the other is getting its claws out and sparing no opportunity to go on a full rampage.

This post is not my attempt to step into this minefield. This is an observation from the sidelines on how some people have seized the moment and capitalised on this historic decision.

While its true that this move gave a natural boost to offerings of financial institutions and financial service providers, none had the speed of response and temerity as Paytm. While pretty much everyone was caught unawares on 8th Nov when the decision was announced, a few were able to recover and respond in order to capitalize on the move.

Paytm brought out full-page print ads congratulating the Prime Minister, with a word play on its tagline ‘Ab ATM nahin, #Paytm karo.’ They did not stop there, but followed it up with marketing to keep the buzz on, while also working on the app to simplify usage for new users, and adding features that helped work around the cash crunch.

Not surprisingly, the bold move was met with staunch criticism & they briefly were caught in the political cross-fire. Paytm's Vijay Shekhar Sharma deftly avoided some of these direct volleys and also took swift steps to recover from few of the moves that turned controversial. Like all controversies, these also added to the brand recall and eventually worked in their favour by adding to the kitty.

It was surprising to see neighbourhood stores and roadside vendors accept cash on paytm in barely a couple of days after the decision. While there are plenty of e-wallet players in India, many who have existed for much longer and few with deep pockets like Airtel, Paytm has managed to stay high on recall and captured the imagination of people. 

Consequently, they have emerged a winner in round one. As the moves towards a cashless society get stronger, there is a lot more action to watch out for in this space.

Evolution of Gramener Design Toolset

Earlier this month, I had written an article in our company blog. I'm reposting it here again:

At Gramener, we have been continuously evolving our Design process over the past years. These improvements have been to stay in tune with the emerging trends in design, adopt industry standard tools and create a custom Design framework that helps us deliver outstanding visualizations.

This post covers the ‘tools’ aspect of the design improvements we’ve implemented, and it discusses the challenges faced and considerations on coming up with a pertinent toolset to cater to Gramener’s core offering of Information Design & Data Visualization.

Earlier Process brief and toolset used:

Until a year back, the primary tool we used during the design phase was paper-pencil for creation of Design concepts, while the actual designs were created on Powerpoint. For most engagements we had a low-fidelity design as deliverable, wherein the paper sketches were translated to a basic representation on MS Powerpoint using snipped images of charts and other basic dashboard components.

In certain engagements, when there was a need to show a closer-to-actual representation, a high-fidelity design was created, again on Powerpoint using imported SVG objects or drawn chart elements. There was almost no prototyping or demonstration of interactivity, save the occasional powerpoint slide transitions. The need for an internal Design library was met by having all designs stored on the Gramener file server and exposed on a searchable, minimalistic UI, that was spruced up with basic previews and meta-tags.

Given the ability of Gramex, Gramener’s platform to quickly pull out charts from the engine’s library and setup a basic, working version of visual dashboards, historically, there was not much of a need for a standardized design tool. Hence, Powerpoint was a quick and light alternative that fit in well with the skillset of Data Consultants, which is a role comprised of functional analysts, who had innate comfort with MS Office rather than the Adobe suite of products.

Evolving needs:

With the evolution of projects done by Gramener and the rapid scale-up in clientele and team size, the need was felt for a rethink of the above mentioned stack. With a large number of first-time visualization adopters amongst clients, we sensed their comfort in reviewing solutions with a high-fidelity design that showed visual design aspects as close to the final solution as possible.

With increasing functional complexity and data size of our visual solutions, Data Consultants had to spend more time in the solution conceptualization and data analysis phases, whereas there was an increased need for additional support during the Design phase.

Challenges faced:

In summary, the key challenges faced with the above simplistic process & toolset were:

• Variation in quality, finesse and look-and-feel of designs created on Powerpoint
• Long cycle time for design creation, with an often cumbersome process for putting together the occasional high-fidelity versions
• Teething challenges in development handover & translation of the design
• Need for multiple design reviews during development phase, coupled with rework
• Difficulty in demonstrating state transitions, interactivity and user flow within a visual application concept

Alternate Solution:

Given these challenges and the additional considerations of scalability & rapid replicability, we went about evaluating changes needed in the process, toolsets & framework. We spoke to the design community and took first-hand advice from experts in these areas. From the tools perspective, we evaluated a variety of visual design and prototyping tools including Adobe Photoshop, Illustrator, Balsamiq, Axure and Pinegrow, amongst others. Based on considerations of fitment to our visualization lifecycle, availability of complementary skillsets at Gramener and ability to address the challenges outlined, we zeroed in on the following:

Sketchapp – for Visual Design:

The vector graphics editor from Bohemian Coding has been rapidly gaining popularity and has quickly built its own community of loyal users. With addition of new role of Information Designer at Gramener, this tool helped us in the following ways:

• We found that the tool was very easy to pickup due to its intuitive usability, perhaps closer to Powerpoint. It also had ample tutorials and a robust support ecosystem
• By design, the tool was meant to create vector objects and naturally fit in better for dashboards and web applications, while other tools were heavily skewed towards graphic design
• Has a thriving ecosystem of plugins for productivity improvement, and importantly provides for easy export of style sheets to aid development translation
• Comes at a relatively economic price compared to popular options, Apple hardware prices notwithstanding

Invision – for Workflow, Prototyping and Design library:

A leading prototyping, collaboration and workflow platform used by several design houses around the world, this tool checked-off multiple items in our requirements list:

• Provides an end-to-end design workflow solution with useful admin features
• Has native integration with Sketch and hence it automatically syncs, imports and stores assets from Sketch files. Automatically creates style sheets & enables direct look-up
• Supports basic prototyping needs to show interactivity and transitions
• Has useful collaboration & commenting features, and integrates live design presentation and review capability
• Doubles up as a repository with versioning & hence can be used as a design library

In Summary, below is the overall process that we have arrived at, which has been working well for us and has addressed most of the above-mentioned issues we faced: