Skip to main content
teamspace
Blog

Tips for testing software

You found a candidate but face the challenge of evaluating it without sinking time into setup and training. Here's how.

Thorsten Lenk 4 min read

How to find a fitting business software

No one likes buying a pig in a poke. A small thought experiment: you have 4 days to test, four candidates in scope. Split evenly, 3 days go into systems you’ll never use. If you could rule out unsuitable systems in an hour each and focus on two, you’d spend your time much better.

Quickly weed out the misfits. Don’t waste time on long manual reading. Ask. Most vendors will gladly answer questions and demo their system.

Clarify upfront:

  • A: What must work?
  • B: What do you definitely want to see?
  • C: Budget, number of colleagues, target go-live date.

Our tips

1. Capture expectations

Write down what you’re looking for and what you expect, in bullet points. Long enough to be specific, short enough to stay focused.

2. Build a criteria checklist

Group criteria by importance:

  • A: Must be met 100 %
  • B: Should be met
  • C: Nice to have

3. Develop use cases

Turn the A and B criteria into use cases: processes you can run through and verify.

4. Get advice

Don’t try to map your use cases into an unknown system alone — too slow, too frustrating. Ask for a product walkthrough so the vendor can clarify quickly and competently.

If you’d rather not contact a consultant first, watch video tutorials. For teamspace see Getting started (linked in the test account and at the foot of the homepage). Tutorials cover basic concepts, but a conversation is the fastest way to verify your requirements.

5. Check exclusion criteria

If a deal-breaker comes up during the walkthrough, stop after an hour and free your time. The same applies later — be direct, advisors prefer a clear no over a long maybe.

6. Test yourself

Once your rough requirements are confirmed, dive in alone after the walkthrough to get a feel for the system. Take notes of every question that comes up — bring them to the follow-up with your advisor.

Testing is teamwork

Your advisor knows the software; you know your processes. Together you make a good team. Good luck testing teamspace!

— Thorsten Lenk

Read on

Reviewed in a requirements check

You have questions on this topic? In a 15- to 30-minute meeting we discuss your specific requirements, free of charge and without obligation.

Share article:

Software that fits your setup?

In a 15-minute meeting we look at your requirements together and give an honest first opinion.