Clear, Concise, Common Language

5 min read

Over the last few months working at Thinking Big, I have encountered small, yet important issues which have taught me lessons on the value of challenging familiarity and thinking, well, BIGGER. If it wasn’t for the small problems I encounter on a daily basis, I would not be able to be as creative and inspired in my work.


Business Process Re-engineering for Digital Enablement

10 min read

The die has been cast: businesses and government departments that do not provide end‐to‐end online services will become like wallflowers at the dance. Invisible and lonely. Customers become frustrated with an online service that goes as far as filling out a form, then they click on submit and end up waiting for days, weeks or longer for their transaction to complete. This is usually the result of a manual process in the backend that involves multiple people executing multiple steps.


Please Don't Forget the User

10 min read

Plain and simple, software and services are used by people. And the user’s experience with those services will decide the success or failure of the enterprise that creates and owns them. And as software becomes software as ­service, it is becoming increasingly more important that companies prioritize the needs and wants of their users.


Communicate Early and Often

5 min read

For the past year, Thinking Big staff have been involved in the Web Renewal Initiative for Veterans Affairs Canada. This initiative is a multi-year project where all federal departments and agencies are migrating one central website, That's over 1500 websites moving to one website, no big deal. Our goal as the project team is to ensure that Veterans Affairs Canada's migration goes off without a hitch.


Prototyping With a Framework

15 min read

In a traditional systems development life cycle (SDLC) project, sometimes the end result does not successfully meet the needs of the user, even though it does meet the requirements set out by the business requirements document. The reason why is simple: no one tests the requirements with real users. Instead the product is released and users experience a sub-par product.