Monthly Archives: November 2013

Quick review: The Fifth Discipline

The Fifth Discipline: The Art And Practice Of The Learning OrganizationThe Fifth Discipline: The Art And Practice Of The Learning Organization by Peter M. Senge

My rating: 3 of 5 stars

I first met systems theory in ministry training post-theological college. This was in connection to pastoral care for people, taking note of the systems in which they live (family, workplace, peer group, church, etc).

This book is all about systems thinking and its use particularly in management. It is an effort to shift our thinking from simple linear cause-effect. In its stead is the more useful conception of two-way and mutual effect. For example, a business downtown might lead to cost-cutting, which causes further profit loss. Or a spouse might flee a difficult marriage by extra immersion at work, worsening the relationship problems.

There may be simple loops like these (positive or negative feedback). Of course many are far more complex, and systemic patterns will overlap to ‘interfere’ with each other.

The contention of Senge is that modern organisations must learn how to learn these systems. The ‘learning organization’ of the subtitle is not an educational organisation. It is one that observes, reflects and can thereby perceive deeper systemic behaviour behind the obvious surface data.

That all sounds a bit tech gibberish – showing I don’t really understand it yet. But that’s ok, because it’s about a way of thinking rather than being able to understand everything.

I think this book, and the ideas in it, is very useful for any kind of team or leadership.

View all my reviews

 


 

User review: Garmin Edge 510

OK, this is a bit odd – I’m reviewing a cycling computer.

I am not even close to knowing all the features of this device. So this is not an expert review, but a user’s view of the Garmin Edge 510 bike computer.

Purchase factors
Here are (some) of things I had in mind that led me to buying this unit, rather than others.

  • I want a GPS computer
    I was using my smartphone for GPS. I prefer to have battery power for making calls
  • I want to measure cadence
    Though far from being a serious racer, I join the occasional club race. Knowing about how I pedal and being able to practise spinning faster are quite useful. This also provides a way to add some interest on days when it’s hard to get out and exercise, though I know I should
  • Bluetooth connection
    I prefer to upload rides via phone, rather than have to get a live computer with USB cable. The 510 model has this, the 500 doesn’t
  • Touch screen
    This is another difference between 500 and 510. It’s much easier to use the screen than find fiddly buttons to scroll through viewing options and settings
  • No need for full maps
    The big brother Garmins (800 and 810) have full GPS mapping. I was not looking for full navigation
  • No need for heart rate
    This may sound odd, because the 510 bundle I bought has a heart rate monitor. I use it a little – but it was a reason I bought the computer
  • Local sale
    I wanted to see and play with a device before buying – and be able to ask for help locally if something went wrong. That is, I wanted a computer I could buy down the road, not just on the internet. I could have gone cheaper via internet, but I purchased at my LBS

Things I like
The computer was pretty easy to set up. This was the first time I’d set up a bike with a sensor magnet on the crank, but it was not as bad as I feared. And the whole unit has no need for wires.

The GPS works very quickly. Actually, the 510 can receive data from two satellite systems: American GPS, and Russian Glonass. (If you want to save power, it’s easy to switch to GPS-only. Or to no satellites at all, for using a stationary trainer.) I’ve been very happy with this part of the computer, knowing that phone GPS has sometimes left me waiting, waiting, waiting. I frequently find that GPS position is set even when the unit is inside my house or under the carport.

Uploading rides over-the-air, though not perfect, is usually pretty smooth.

The touch screen works well, once you adjust to it not being a phone. I’ve seen complaints about the screen being a pain, but all it needs is firm contact. This is great, because I can use the screen on winter’s coldest ride while wearing full-finger gloves. A smartphone-like screen would require bare skin. And frostbite.

I have made use of the capacity to programme the screens. You can display the data you’re interested in: speed, distance, cadence, heart rate, time, elapsed time, power, percentage of maximum heart rate, etc. It’s an easy task to alter what you see, and have a few set screens to use for different types of ride.

Garmin 510

What I don’t use
The computer is much more than an instantaneous read-out. The menus tell me that I can store courses or make some kind of training plan. I haven’t.

The Garmin 510 can connect to a power meter, if you have one. I don’t.

Irritations
Bluetooth can be irritating, and was especially so early on. I could not get the phone and GPS unit to talk nicely. It bugged me enough that I went back to the shop for advice. They suggested Garmin support, who responded quickly. They tried to be helpful but the basic message of all my contact came down to this: ‘Bluetooth is weird.’ (That’s my summary.) Since then there have been a few firmware updates. These seem to have almost eliminated the Bluetooth problems. Sometimes still the two units sit next to each other, Bluetooth on, not connecting for minutes at a time. Running software version 2.80 (just this week) seems to have made this quirk more common.

( Edit: Bluetooth is worse for me with version 2.8. After a ride I often have to switch on Bluetooth, switch off the Garmin, wait, then switch Garmin on again before out will connect with the phone.)

The heart rate system is irritating, too. Though this was not a major feature I sought, it came with the package. So I’ve tried to use it. The sensor and computer unit connect easily enough. But the readings are inconsistent. Garmin’s instructions tell me to moisten the contact points on the sensor. I always do this, without going so far as soaking my body in cold water. Sometimes it works. Often I see readings impossible to believe.

This week, for instance, I went for a ride I called ‘A Tootle’. I was just rolling around, with no great efforts. But my HR, apparently, was frequently over 200bpm (see below). I don’t think my heart can do that!

HR

 

Sometimes the HR worked perfectly while assisting juniors but went haywire in the half-hour gap before senior racing (when the information might be useful). If you ever see me riding along and it appears I am adjusting some type of underwear at chest height, please be assured – it’s only the heart rate sensor! And it’s driving me crazy yet again.

Summary
This unit has been very good for my purposes. I’m glad I bought it, and it achieves what I want. There are many tech features I don’t tap in to, but those I use almost always deliver exactly as promised.

 

 


 

 

God’s shepherds

The Bible is full of sheep. And shepherds.

Many leaders were actual herders. Abraham had plenty of livestock (Genesis 13:2). Jacob, while caring for the flocks of his father-in-law Laban, received abundant ovine blessing (Genesis 30:43). Joseph labelled all 12 sons of Israel as shepherds (Genesis 46:34). Moses spent forty years herding (Exodus 3:1, what is it with caring for the father-in-law’s sheep?). And king David famously practised to defeat Goliath by protecting sheep (1 Samuel 17:34, being unmarried David worked for his father).

Being familiar with sheep farming, Israel understood shepherd imagery applied to God. Even in the Bible’s first book God is named shepherd (in this case, of Jacob Genesis 48:15). God as shepherd appears in many places that are not even that famous psalm (I’m trying to avoid the too-obvious reference), for example Psalm 80:1 or Ecclesiastes 12:11.

Yet the Lord is not the only figurative shepherd in the Bible. God regularly calls the leader(s) of his people by that same term.

God summarises the job of the judges in a single command: shepherd my people (2 Samuel 7:7). David, even before he was king, was a shepherd of Israel (2 Samuel 5:2). Supremely, Jesus is the good shepherd (John 10:11-16). The privilege of Christian leadership is to be a sheep who serves the chief shepherd by shepherding other members of the flock (1 Peter 5:1-4).
Farm feeding tour
Shepherding problems
As far as I can see, there are two major problems regarding sheep-shepherds. The two, sadly, end up with the same ill outcome.

First, sheep might be neglected – sheep without a shepherd. Moses prayed that, after his death, Israel be given a leader to avoid this problem (Numbers 27:15-17). Jesus was full of compassion precisely because he knew the people were shepherdless sheep (Mark 6:34). Without shepherds, the sheep are aimless and hopelessly lost.

The second problem is abuse of the sheep by those who have oversight. Ezekiel delivered a sting to the self-serving shepherds of Israel (Ezekiel 34:1ff). They were using the sheep, but not protecting them. The shepherds fed themselves, and starved the sheep. Unfortunately, the shepherds of Israel developed immunity against prophetic stings – there was no reaction at all.

In the time of Ezekiel, this second problem morphed into the first. Abusive shepherding led to sheep being scattered from safety (see verse 6). So the abused flock also became a neglected flock.

In light of this, I return to Peter’s instruction to church elders. This is how they are to care:

Shepherd the flock of God that is among you, exercising oversight, not under compulsion, but willingly, as God would have you; not for shameful gain, but eagerly; not domineering over those in your charge, but being examples to the flock.

Peter steers us away from the two errors. First: be a shepherd, willingly, in accord with God’s will. Second: don’t abuse your position.

Since this post has circumnavigated a large area of Bible, I think it’s only fair to end with an attempt at summary.

  • If you’re in the flock, follow a good shepherd. Jesus certainly is that. And Jesus has appointed under-shepherds for good reason – we need them
  • If you get to do some shepherding, then do it. Don’t back out of the responsibility, and be intent on leadership that does not harm the sheep

 


 

Generalisations, stupid & sensible

While at theological college I learned heaps. Mostly this was gradual and grain by grain. There were few ‘light bulb’ moments when a whole new thought clicked into place.

But I remember one light bulb experience.

It concerns generalisations. A fellow student, disgruntled for some trivial matter, shared his general view. “The trouble with all the rectors of Sydney is …”

What an insight this was for me – that a young student believed he had enough knowledge to generalise about well over 200 senior ministers. He knew! My flash of learning: what a stupid thing.

It’s not that generalisations are a problem. It’s that some generalisations are a problem. There are sensible generalisations and there are stupid generalisations. That day I decided I could not trust this student’s generalisations. But I immediately thought of a number of friends whose generalisations I trust.

generalisation T-shirtGeneralisation T-shirtI hear people make all sorts of general comments. They can be about men, women, single people, child-raising, churches, atheists, journalists, sports people, musicians, … I try to be careful, even wary. I want to know why do you say that?, how did you reach your that conclusion?

Many relationship issues arrive packaged as a generalisation. ‘My kids never listen.’ ‘My Bible study leader has a grudge against me.’ ‘My boss hates women.’ ‘My wife has no interest in sex.’

Church conflict shares the same packaging. ‘This church is not friendly.’ ‘No one trusts the pastor.’ ‘All the men are lazy.’ ‘The music team isn’t trying.’

What to do?
I suggest the best way to avoid stupid generalisations is to delay making sweeping statements. Before drawing wide-ranging conclusions, stay with the messy specific details. Listen first, speak later, and really delay anger (yes, it’s James 1:19).

Take the above example: ‘My kids never listen.’ That’s the generalisation – it’s one that can hurt both parent and child. The parent treats it as a universal truth, and might give up trying. The child will pick up what’s going on and likely conform to the expectation.

It’s usually more helpful to deal with specifics. Asking, ‘Why do you say that?’ might lead to: his room is still messy though I told him to clean up; during dinner I asked her about school but she didn’t really acknowledge me; it’s a busy month, so I need to make most of our time together, but it’s not working. Listen to the person, listen to the situation, listen to the details. There might then be a specific way to change.

Just this year I stumbled over the same idea expressed slightly differently. In The Fifth Discipline, Peter Senge warns against the ‘leap to abstraction’. With concrete evidence of short, impersonal staff meetings we might abstract a conclusion that the manager dislikes people. What we did not know is that she has a hearing problem made worse in group settings. Senge says to beware the leap to abstraction. Deal with the concrete as much as possible. Good advice.

 


 

Bike for Bibles

On 4-5 November, three Little people (Ruth, Nahum & Chris) joined the Bike for Bibles crew assembled at Bright to ride up some hills.

Bike for Bibles is associated with the Bible Society, and raises funds for Bible distribution and literacy. As I write today, the fund-raising page for the whole team of riders indicates a total of $6624. I certainly am thankful for those who have donated through the Littles, so want to say so publicly. Thank you!

For your interest, here’s a touch of information about the two rides we did (the whole team completed four rides – but we were unavailable for the first two days).

Monday – Omeo to Dinner Plain

We drove over Mount Hotham to Omeo, in order to ride back up the hill. Good idea in theory – until we saw it snowing on Hotham and at Dinner Plain. (Thinks, “Did I bring enough warm clothing?”) We left Omeo with no warm-up and straight into the steep part of the climb. The first 9.5km are the most consistently up, though there is a steepish bit just before the finish at Dinner Plain. This ride, though it had lots of elevation gain, felt less like mountain-climbing and more like a very hilly country ride. We saw not one other cyclist coming up from Omeo

Vertical elevation gain: 1816m according to Garmin Connect, or 1979m according to Strava.

Here’s the Strava ride analysis (note: the ride was to Dinner Plain, but two of us went on to Mt Hotham after a leisurely rest).

Here’s a photo from Dinner Plain.

 

After riding from Omeo

After riding from Omeo

Bright to Mount Buffalo

On day one I got into my own rhythm, but on this day I stayed at a relatively easy pace at the back of the bunch. I’ve ridden Buffalo a few times, and it’s a beautiful trip. Great views, feels like a real mountain climb. And this long weekend there were dozens of cyclists on the road.

Here’s the Strava record:

And a short video of Ruth, about one third of the way up.