Since really the beginning of the Australian web design and web development industry, we’ve been building websites and applications for clients. It’s been a long journey, though we can comfortably lay claim to a very significant expertise in that we continue to invest in our clients and their online businesses.
It's important to our clients to understand how we’re different and why our clients choose Wiliam.
We're passionate about what we do. We want to constantly improve. We want to continually surprise and delight our clients. We want to achieve significant success for them. We need to understand their businesses and what works for them.
We don't cut corners. We don't outsource our work. We don't pretend to be something we're not.
If Philip can have one L or two, why can't Wiliam?
The truth about our name?
We're named after a small, Egyptian hippopotamus housed at the Metropolitan Museum of Art, New York; he is their mascot and they call him William.
When we designed our first logo, we could only fit six letters:
W I L
I A M
So we dropped an L.
Queron head’s Wiliam’s Analytics, Data and User Experience
Queron and his team develop the frameworks on which Wiliam builds its websites and applications by understanding our clients and their data, building prototypes & architectures and working with users & customers to design intuitive and functional interfaces and experiences.
Queron is fascinated by the concept of ‘touch’ and where it is leading interface design. Queron is also fascinated by working lunches and during his time with Wiliam, has managed to invite himself to the unveiling of every single platter of sandwiches or sushi, whether his client or not.
Ed is Wiliam’s Creative Lead, running an award-winning team of interface and creative designers.
Working closely with our UX teams and front-end developers, Ed and his team are responsible for our client’s brands and the visual designs and experiences of our client’s websites. Ed’s team work on a broad range of projects, from small online marketing assignments to interfaces for significant websites in retail, banking and eCommerce.
It’s a handsome team and it looks the part with folios, Lamy pens, Wacom tablets and Powerbooks, and a small fish they call #Hex.
Collaborating with a client through the initial design brief stage is of huge benefit to the future outcomes of a project
Matt run’s Wiliam’s Technology and Development team, Wiliam’s team of Microsoft developers and programmers.
Working as a Solutions Architect, Matt is responsible for the development, maintenance and optimisation of our client websites and applications. Given the size and critical nature of some of our client websites, this is no small feat, especially across time-zones.
It would be remiss not to mention our developer ponytail to non-ponytail ratio of 1:6 (a good ratio for any self-respecting development team) or that despite a shelf of Coke Zero in the fridge, no developer will touch it. Opting instead course, for the real deal on the shelf above.
Following on from my previous blog about thread exhaustion, I recently had to deal with a site experiencing thread exhaustion that happened to be an Umbraco site. This issue was nothing to do with Umbraco itself, it was synchronously calling a fairly slow webservice that was responsible. My solution? Async controllers
Our work is challenging and evolving and that’s why we enjoy it so much… because we’re evolving.
It’s a great thing to enjoy your work and have fun along the way.
Trust. Respect. And humour. We’re all in this together and we’re friends after work. We’re all equal and we’re all honest with each other.
We’re grounded. Very grounded. We’ve been doing this for a long time and we don’t need to stand out.
We don’t pose and we don’t use technology for technology’s sake.
We enjoy fried food and will admit to that.