Tag Archives: tools

Change mapping, tools for change: Tetradian on Patreon

I think you might be really interested in what Tom Graves (Tetradian) and Joseph Chittenden are doing on Patreon.

Their work is relevant for anyone involved in making change happen in organisations, i.e. you, me, regular people, and those in roles such as line managers, project managers, programme managers, product managers, product owners, system owners, business architects, enterprise architects, business analysts, software architects and so many others.

Beyond labelling

Project management is bad, product management is good. Estimates are bad, forecasts are good. Management is bad, leadership is good. MBAs are bad, MFAs are good. This is agile, that is not. This is lean, that is not.

Such focus on labelling and promoting one idea at the expense of another does not give me much these days. Instead, I am much more interested in learning about different schools of thoughts, hearing nuanced perspectives, and understanding in which context and for which purpose different traditions developed.

I am much more interested in attempts of integration, such as Jesse James Garret’s The Elements of User Experience: User-Centered Design for the Web and Beyond and Milan Guenther’s Intersection: How Enterprise Design Bridges the Gap Between Business, Technology and People, than any attempts of establishing one tradition’s superiority over all others.

This is also true for topics beyond technology, and perhaps even more important there.

We need all the help we can get if we want to deal successfully with the big and small challenges we are facing today. This means selecting our tools wisely and not rejecting potentially useful tools because of their origin or any label they may carry.

The Oath of Non-Allegiance promotes a similar view. I begin to wonder whether signatories (myself included) should be required to re-read it, reflect on it, an re-sign it if they still believe in it every quarter or so.

Testing websites with Nightwatch.js

A colleague introduced me to Nightwatch.js which is described on its website as follows:

Nightwatch.js is an easy to use Node.js based End-to-End (E2E) testing solution for browser based apps and websites. It uses the powerful Selenium WebDriver API to perform commands and assertions on DOM elements.

And it seems to do what it says on the tin in a refreshingly simple way. We took Nightwatch.js for a spin on an e-commerce site and where amazed how quickly we achieved some promising initial results.

I’m sure there are other, perhaps more sophisticated, test solutions that can do all sorts of interesting things, but I think Nightwatch.js might be very useful in quickly building a safety net of automated tests for a new website being built or for an older one with insufficient test coverage.

I’m looking forward to spending more time with this tool and I’d be interested in hearing about others’ experiences with it.

Just so that I said it explicitly: I haven’t yet used Nightwatch.js in anger or for a longer period of time, so please read the above in this context.