01 logo

Shane Murphy: Designing a Cambridge Mobile Experience for Occasional Customers

A service should remain understandable when using it is a small part of someone's life.

By Shane MurphyPublished 5 days ago • 3 min read
Shane Murphy: Designing a Cambridge Mobile Experience for Occasional Customers
Photo by Vitaly Gariev on Unsplash

An occasional customer should not have to become an enthusiastic customer to receive a good experience. Some people want a mobile service for a handful of calls, a few messages, or a particular recurring activity. Their needs are modest, but their questions can be important. I think product design often becomes more revealing when we consider someone who visits infrequently, remembers little terminology, and has no interest in exploring every feature. The experience must stand on its own each time that person returns to it.

I am Shane Ian Murphy, a former cofounder and Chief Business Development Officer of Limitless Mobile. My preference is to treat low frequency use as a legitimate pattern, with its own design requirements. It should not automatically be framed as a problem waiting to be corrected through greater engagement. A customer who spends very little time thinking about a service may be expressing a clear preference. Respecting that preference means making the essential arrangement easy to find, understand, and revisit without a lengthy learning process.

Consider a fictional Cambridge resident, Martin, who mainly uses his phone to arrange a weekly walking group and receive occasional messages from relatives. This is a fictional customer example, not a reported interaction. Martin does not want a daily stream of service information. When he does need to check his arrangement, he wants to answer three ordinary questions: what is available to him, whether he needs to take any action, and what a possible change would mean. His experience should be designed around those moments of attention.

The first useful decision is what to show before asking Martin to explore. A concise account overview could explain his present arrangement in familiar words and give any relevant dates clear labels. Optional features should remain available without crowding out that explanation. I would also avoid assuming that an infrequent visit indicates confusion. Martin may know exactly why he is there. A direct route to his question respects his time more than a guided tour that insists on introducing things he has already chosen not to use.

Remembering terminology is another unnecessary burden. If Martin encounters one name during purchase and another when he returns months later, he must work out whether the underlying arrangement has changed. Consistent language helps him recover his understanding quickly. Where a term has genuinely changed, a short explanation should connect the old and new descriptions. The same principle applies to messages: say what the message concerns, why it matters now, and whether anything needs doing. An announcement without a clear relevance test is an invitation to ignore the next announcement.

Choice should be presented with proportion. Martin may be interested in a different option for a particular month, but that does not mean he wants an elaborate comparison of every possible feature. I favour a small comparison organised around the activities he named. What changes for his weekly arrangements? What continues as before? What dates or actions accompany the change? A seller should be comfortable explaining that the current arrangement still fits if the alternative adds little to the customer's stated purpose. Useful advice sometimes confirms an existing choice.

Support also needs to work after a long gap. Martin should be able to describe his issue using the words available to him, without being tested on a process he last encountered several months ago. An adviser can establish the relevant context, explain the next action, and check that the explanation makes sense. That is a different rhythm from helping a frequent user who already knows the interface. Neither customer deserves a better standard of care; they simply arrive with different amounts of recent practice and different expectations of the conversation.

The fictional Cambridge example suggests a valuable design question: could Martin leave the service alone for a while and still understand his next interaction? If the answer requires several reminders or a return to introductory material, the experience may depend too heavily on habit. I would aim for calm, self contained moments of clarity. Occasional customers should be able to remain occasional. Their success is having the service ready for the role they gave it, while preserving their freedom to spend attention on the rest of their lives.

mobile

About the Creator

Shane Murphy

Shane Ian Murphy: co-founder/partner, Tri-Party Tokenisation; founder/CEO, Global Secure Technologies (planned 2027 launch); co-founder/partner, Dual Party Capital. Partner, RougeN International Corp. Formerly of Limitless Mobile.

Enjoyed the story? Support the Creator.

Subscribe for free to receive all their stories in your feed.

Subscribe For Free

Reader insights

Comments

There are no comments for this story

Be the first to respond and start the conversation.

Sign in to comment
    Written by Shane Murphy