A small question
For a utility, it could be whether a second entry step can disappear. For a game, it could be whether the next move is clear without a written instruction.
In development
We develop our own utilities and games alongside our work for clients. For a utility, we test whether it makes a recurring job easier. For a game, we try the central mechanic in a playable build before adding more rules.
Utilities
A utility has to earn the space it takes up on a phone or a desktop. We start with one repeated job and pay attention to how it is done today. Opening the tool, entering the information and getting the result all count towards the effort.
A useful prototype lets us try the whole job with ordinary data. It should also show what happens when someone leaves halfway through and comes back later.
Games
For a game, the first question is how it feels in the hands. A small playable build gives us something to try. The timing of an input, the way a move is acknowledged and how quickly someone can try again all affect whether a rule makes sense.
Keeping a prototype to one mechanic makes those details easier to judge. New levels and artwork can wait until the basic interaction holds up on its own.
For a utility, it could be whether a second entry step can disappear. For a game, it could be whether the next move is clear without a written instruction.
A screen sketch can settle the order of a task. A working build is needed to test timing, saving a draft or returning to play.
We keep what helps, revisit the awkward parts and can shelve an idea that needs more effort than the result is worth.
For a client project, tell us who would use it and which part you need to prove first. We can discuss a prototype or a first release with a defined handover.
Discuss a product idea