Dear Community Developer, Help us Help you
A Dangerous Trend
have been trying to look into the asked questions on the developer forum, and while I would be able to answer many of them, I do not feel comfortable doing so.
This is because I simply do not know why the developer is asking their question.
The ServiceNow community thrives on the collective wisdom of its members, yet the path to true progress hinges on understanding the "why" behind each query. Oftentimes, developers find themselves immersed in a sea of questions and requirements that lack context, making it challenging to offer the most helpful and relevant solutions.
Take, for example, the infamous "blue button" dilemma – the request is clear, but the underlying motive remains shrouded in mystery. In a vibrant ecosystem brimming with talent, it is vital to leverage the expertise of those who offer their time and know-how to the community. To do so, developers must be forthcoming with the rationale behind their requirements, enabling others to provide more nuanced and informed guidance.
This becomes even more crucial in light of the gamification system that permeates the ServiceNow community. While it fosters healthy competition and motivates many to strive for excellence, it may also lead to solutions that, though deemed helpful, are not necessarily the most optimal or pertinent.
Ultimately it can become excessively expensive for the organization that owns the ServiceNow instance that you are developing for, as well as any other ServiceNow-owning organization whose developers are looking at your solved community question without regard for the context of the original requirement.
Let's Be Better Together
To truly excel as a ServiceNow developer, you must adopt a holistic approach that goes beyond technicalities.
Asking the right questions is paramount: understanding the who, what, when, where, and most importantly, the why, can unveil a myriad of opportunities for innovation and improvement.
By delving into the business perspective, developers can propose alternative, more effective solutions that cater to the actual needs of the stakeholders.
When posing questions on the community portal or evaluating requirements, it is essential to consider factors such as objectives, involved parties, context, pain points, and success criteria. By embracing this comprehensive outlook, developers can harness the full potential of the ServiceNow community and contribute to a more connected, insightful, and impactful future.
Want to Know More?
Read the official ServiceNow resource on creation of User Stories, as well as my other blog on gathering requirements.
| More content by Jakob Anker Nielsen |
1 Comment
