Form mockups - what do you do?

[karenlamano]

I created some visio shapes to help create a mockup of what the form will look like (not the ESS view) so we can provide a visual and get signoff from the service owner prior to development.   We found that this helps to nail down the exact requirements and also reduce the rework when creating catalog items (rather than having a developer change/rework after a service owner see the initial form).

Has anyone else run into this issue? Rework because the form/workflow isn't mature or doesn't exist yet so the service owner has lots of changes while in development? If so, how do you handle it and what has helped?

This is what it looks like, I can't attach the visio shapes since .vss file isn't allowed but if you want it, message me thru the community.

[JeremyDallasTX]

The old ones are available here:   https://servicenow-my.sharepoint.com/personal/jeremy_smith_servicenow_com/_layouts/15/guestaccess.as...

karenlamano might have some new ones....

[tbutton]

I used to do wireframe Mockups for web stuff in another life. Visio is fine, but you can also use Adobe Fireworks since thats what its for. The benefit of using Fireworks is that you can add visual functions to work like buttons, popups, etc.. The downside is that there is a learning curve to Fireworks, but if you have used any other Adobe Products it should translate.

[annettem]

Hi Timothy

I too have used wireframing tools, such as InVision, to help create mock-ups of what a webpage will look like. I agree with previous comments that the advantage of creating a mock-up is that you save developer time, not just when delivering a service catalogue, but also with many other applications, including custom apps. I'm surprised that ServiceNow hasn't embraced this opportunity yet.

Here's a useful review of a number of wire-framing tools, including some open source ones - The 18 best wireframe tools | Creative Bloq . I tried Pencil and found it pretty easy to use but sharing the designs it is not so easy unless people install the software on their machine, which most corporate users won't be able to do.

As the original posts were made in 2014 it would be interesting to hear of people's thoughts and experiences since then.  

[bernyalvarado]

Very interesting discussion. We have a great design team in our group, and we go through all the good design artifacts/process for our non-ServiceNow projects (IoT, Security, Data Visualization, Etc...). Despite of mastering the "art of design" so far our experience with ServiceNow's project it has been that it's faster and more effective to do the changes directly in the form and show these in there. This can be done within the Development instance. Doing changes to a form these days in ServiceNow takes about the same time that it will take to do the changes in other systems (Powerpoint, Sketch, Visio, InVision, etc...). On the other hand, UIs & Experience for ServicePortal projects is a different discussion all together

Thanks,

Berny

[Kalaiarasan Pus]

I have used Balsamiq briefly in the past and found it to be useful to a certain extend.

But now, I am with Berny on this. I find it actually much easier and quicker now, to do the mock ups on ServiceNow and try to use my developer instance whenever feasible.