How does your company buy technology?

1. 01 / 06

   How does a technology project usually get started in your company?

   a From a concrete problem someone measured or suffers every day. b From a tool we saw working at another company, or in a demo. c From the feeling that we are falling behind.

2. 02 / 06

   Of what you bought or built last year, how much is in use today?

   a Practically all of it: it is part of the daily operation. b Part of it — there are licences and modules nobody opens. c I do not know. And yes, that is also an answer.
   ← Back

3. 03 / 06

   Who decides that a project is “finished”?

   a The vendor: they deliver, invoice and close. b We do, when it works in the test environment. c The business: when people use it in production and it solves the problem.
   ← Back

4. 04 / 06

   How many “closed” projects still have not solved what they were meant to solve?

   a None that I can recall. b There is one or two. c More than one — we have systems that are half-used or worked around.
   ← Back

5. 05 / 06

   How do you pay your technology vendors?

   a By the hour or by the month, with no scope saying what must end up working. b Per project, but the scope stretches and so does the cost. c Per stage with defined outputs: payment against something that works.
   ← Back

6. 06 / 06

   When a project runs late, who absorbs the cost?

   a We do: more billed hours, more months of contract. b It depends on how each one gets negotiated. c The vendor: the scope was closed.
   ← Back

Processing…