Shane Murphy on Global Secure App: Making Support Part of the Design
An interrupted journey needs a clear explanation and a realistic next step.
The Global Secure App concept brings proposed service categories into a shared interface. That design ambition needs to include the moments when a person cannot complete their task. I am Shane Ian Murphy, writing from the founder's perspective about the intended experience. This article does not assert that a support arrangement or a particular recovery feature is already operational.
A combined product can make a support question harder to interpret if it does not identify the service concerned. A person may know only that something did not happen as expected. The interface should help establish whether the question concerns access, an activity record, a proposed connectivity service or another part of the experience.
I would want the wording to reflect what the system actually knows. If it cannot confirm a result, it should not imply that the action definitely failed. If a review is still pending, it should not suggest that repeating the request will necessarily help. The correct instruction depends on the implementation and the arrangement behind the service.
For Global Secure App, support design is therefore part of the product model. It concerns the information shown on screen, the way a question is routed and the record available to the person seeking help. A unified brand should make that route clearer rather than conceal the relevant responsibility.
An error message often reaches a user at the least convenient moment. They have tried to do something and now need to understand what happened. A vague or overly technical sentence can add a second problem to the first.
Imagine a fictional app where a document upload fails. A message showing an unexplained code tells the person very little. A message saying “try again” may also be inadequate if the system has not established whether the earlier attempt completed. The wording needs to reflect what the service actually knows.
I would begin with three editorial questions. What can be stated accurately? What does the user need to decide? What action can the product reliably support? The answer may be to check the current status, choose a different file format or contact a clearly identified support route.
An error message should avoid assigning blame when the cause is uncertain. It should also avoid promising that a particular action will fix the problem unless that is supported. Calm, specific wording is more helpful than either an alarming warning or cheerful reassurance.
As Shane Murphy, I consider this part of product writing rather than a finishing detail. The message shapes how a person interprets the service at a point when confidence may already be weakened.
The review should include the surrounding screen. A useful sentence can still fail if its button is ambiguous or the information needed to follow it is hidden. Words and interaction need to support the same next step.
A good error message cannot remove the underlying failure. It can reduce uncertainty, preserve an accurate account of the situation and help the user make a sensible decision about what to do next.
Consider a fictional interruption during the selection of a mobile data plan. The person needs to know whether anything has been purchased, whether activation is pending and where to see the current status. A generic instruction to start again may leave all three questions unanswered.
The support explanation should use the same stages as the rest of the interface. If the product distinguishes request received from completed, the help material should preserve that distinction. Otherwise, the person receives two competing accounts of the same event.
My aim is for Global Secure App to be explainable when the journey is interrupted as well as when it goes smoothly. The proposed design should help a user identify their position and find an appropriate next step. That requires clear language, reliable status information and support routes that match the actual services. It cannot be achieved by reassurance alone.
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.
Comments
There are no comments for this story
Be the first to respond and start the conversation.