I spend a somewhat regular portion of my time answering questions around scalability with WooCommerce. Questions such as “I have a catalog of 600k products, can WooCommerce handle that” and “how many orders can WooCommerce handle” are not uncommon. That said, an interesting post by Chris Lema around scaling WooCommerce brought to light a metric I’ve long felt to be a worthwhile metric for measuring overall performance of any online store; “add to cart” events. This metric is great for measuring not only how well your store performs as you receive more traffic, but how well your store is performing overall as well.
You know, I so often experience small moments of gratitude, in which I then attempt to remind myself to blog about those moments “at some point in the future”. Today, I’m rectifying that by blogging about two such moments right away.
I worked this morning at The Hatch, a small local coffee shop by the beach nearby to me. The staff there are friendly and attentive, and always go above and beyond to assist, despite the establishment not being very busy, which could easily result in a dip in motivation. They’re open and honest, and always friendly.
You’ve launched your product. Customers are purchasing and everything is going really well. You’ve reached the point where your product contains all of the features you feel are necessary in the core offering, yet you want to expand. Today, I’ll be sharing my thoughts on how to expand once having reached this perceived plateau.
You’ve found a customer segment who really needs your product, developed a minimum viable version of your product and have launched to your market. Your customers are purchasing your product with roars of cheer and glee. What you do next is what you’ll be doing for the foreseeable future of your business; maintaining your product. While extremely important, maintenance of a single product can sometimes become repetitive. It can be great to switch gears from time to time.
Today, I’ll run through a few ideas on how to avoid the repetition as much as possible.
Many folks, when asked what they like, proclaim to know. Using movies as an example, many would say “I like action movies” or “I like a good comedy”. I don’t believe this is the most accurate response. Today, I’d like to unpack why I believe this.
All too often we are faced with roadblocks, hurdles and limitations within everything we do. Whether it’s in our personal, work or digital lives, there are often items which stand in the way of us achieving our goals. Success, however, comes flooding through when we remove or refactor these limiting beliefs.
Today, I’d like to share the story of how I removed a limitation, and submitted my first patch to WordPress core in the process.
I pride myself on being someone who is keenly aware of the underlying meaning of words and the ways in which we say them. Being this way is both a gift and a curse, yet it forces me to be very conscious of the words I’m using to express myself.
This is all well and great until you realise you’ve been misunderstood. *gasp*.
I’ve recently been thinking a lot about the role perception plays in how we respond to life and how we receive the various inputs the world has to offer. One particular thought has been around the role confidence plays in shaping our perception.
In many perceptions, structure is synonymous with “boundaries”, “limitations”, and “restrictions”. This is often the perception of the creative thinker. “Don’t box me in” is an often used phrase. As a product person, I feel the role of a product person within a software team is to bridge the gap between how creatives and how analytical thinkers perceive structure. I see structure as fuel.
This week, I’ve begun doing a rotation with our support team at Automattic. Every Automattician does this as part of their on-boarding, as this helps to learn the systems, tools and users we’re interacting with every day. For me, this additionally helps to learn more about the users we’re building products for, which is a huge added bonus towards our user-centric approach to product development. Through this week, my work time demands 100% of my focus to be on the support rotation. I take this very seriously and am 110% focussed on learning as much as I can. This means, of course, postponing or moving any meetings I have on my calendar. This brought about some interesting and exciting results, which I’ll be exploring further here.