Skip to main content

Things That Get in the Way of SE at an Organisational Level (Kotter chapter 1)

Sometimes in a corporate organisation there are issues with the structure and mentality that can get in the way of change taking place. Scripture engagement is all about seeing change happen in the lives of people and communities as they engage with God through the Scriptures. Therefore some of the books about theories of change are helpful to us as we investigate issues within our family organisations. Here is a list from John P Kotter's book, Leading Change, p 16:

  1. Allowing too much complacency
  2. Failing to create a sufficiently powerful guiding coalition
  3. Underestimating the power of vision
  4. Undercommunicating the vision by a factor of 10 (or 100 or even 1,000)
  5. Permitting obstacles to block the new vision
  6. Failing to create short term wins
  7. Declaring victory too soon
  8. Neglecting to anchor changes firmly in the corporate culture
All of these can be an issue in our family of organisations. Here's why:
  1. We allow ourselves to believe our own propaganda about the importance of peoples' 'heart language', and how all we need to do is provide Scripture in that language and God will do the rest. We also underestimate how hard it is to change these well-embedded views in our organisation - folk need to understand that Scripture engagement needs to be embedded within a translation programme from the its very conception
  2. The Scripture engagement (SE) department is seen as 'small' and not as important as e.g. the translation department. SE is viewed as an optional add on. Senior management needs to get on board with the SE vision. I recently overheard one CEO say, 'The main reason Scriptures aren't used is because they aren't translated yet.' That person needs to go and read Wayne Dye's Eight Conditions of Scripture Engagement
  3. We underestimate the importance of SE. It might be an integral part of our vision statement, or mission statement, but we ignore that fact and do what we have always done. Programme managers are unable to succinctly state the vision for the programme they manage, and get bogged down in details ("We can't get the staff, applying for funding takes too much time", etc.)
  4. Students of linguistics and Bible translation rarely take many (or even any) classes in SE, which means that when they reach their area of future work as a translation advisor (TA) they have little vision concerning the impact of Scriptures in their area (or a very over-optimistic view of the usefulness of Bible translation - see point 1). We need to reach hearts and minds early on in their career, and also reach out to those who have been in the organisation for some years to help them to change
  5. The old guard are allowed to stand in the way of change, which means we keep making the same mistakes over and over again, or the structure of the organisation gets in the way. For instance, if we say, 'We want transformation' but then pay for verses translated per day, there is a mismatch in what we are prepared to fund vs. what we want to see happen. Also, the translation department is allowed to have more clout than the SE department
  6. We are only interested in outcomes (change we see as a result of the project) as impact stories in order to gain financial sponsorship, not as ways to motivate the translation team to greater zeal in seeing portions of Scripture distributed and in use. We need to build in clearer performance statements that include the monitoring of the outcomes we want to see, such as peoples' lives being transformed
  7. The New Testament or Bible dedication is seen as the end of the project. The SURAM (Scripture Use Research and Ministry) report in PNG recommended that TAs stay on in the language area for a couple years after this to engage in SE and other ministry. Another issues is that when changes are introduced at the top level of the organisation, insufficient time is allowed for them to trickle down to the working coal face. It takes more than a couple of years for change to really filter through to every level of the organisation
  8. Our corporate culture is very slow to change. We still prefer to finance translation of verses over use of those same verses. The latter is seen as someone else's job (though the very existence of SE specialists means that we do have people set aside to make sure Scriptures are used). What needs to change is "the way we do things here" i.e. attitudes need to change. Sometimes we appoint people who like to keep to the status quo into CEO roles, when what we actually need is someone who wants to see change take place, and is on board with the new vision of the organisation. Organisational culture needs to change, and as I wrote above, this takes time 
There is some good news: 'These errors are not inevitable. With awareness and skill, they can be avoided or at least greatly mitigated', writes Kotter. I hope to write more as I read the rest of the book. See below for the full bibliographic information:

Kotter, John P., Leading Change (Boston, Mass: Harvard Business School Press, 1996).

Comments

Popular posts from this blog

Asset Based Bible Translation (ABBT)

Many of you will have heard of asset-based community development (ABCD). How can Bible translation programmes be asset based, rather than deficit based? The best way to look at this is a comparison table: Deficit based Asset based Driven by outsiders Driven by the community Outside funding Community funded Done to meet a need Done to help the community grow Quality control done by a consultant Community checked and approved Control from outside-in Lead by stepping back Products not accepted? Products are accepted Little engagement Engagement with products Scientific Organic Not sustainable Sustainable Of course many translation programmes these days are neither one nor t'other, they are somewhere between these two extremes. Nevertheless, this illustrates a point, and shows that the current

A Flow Chart for Bible Translation (a Relevance Theory Approach)

One of the current theories behind modern translation work is Relevance Theory. [1] Here is a flow chart that explains the process often used to produce a draft when using such an approach: *Make sure your translation committee makes the decision as to what kind of translation they want. A domesticated translation is one that submits to dominant values in the target language [2] whereas a foreignized translation is one that is happy to import foreign terms and ideas from Hebrew, Greek, or the language of wider communication such as the Greek term baptizo . The chart looks something like this: Text                                   Communicated Ideas                  Context A sower went out to sow  A farmer went out to sow grain   People scattered/threw seed etc. The text has very little information, but behind it is the idea that seed was scatted by throwing it from a bag carried round the farmer's shoulder. This could be explained in the para-

Asking the Right Questions in Bible Translation and Scripture Engagement Planning

If you want to get useful answers you have to ask the right questions. Do you agree? Yes, of course you do. In the Bible translation world we often ask a very narrow question when planning for the next stage of work: 'What would you like to see translated next?' Now, if you simply want to translate, and that's it, that question is fine, but what if you want to see some kind of result from your translation work? What if, for instance, you want to see transformation occur? Then a more powerful question to ask the community and positive stakeholders in the project would be: 'What kingdom goals would you like to see reached?' These kingdom goals should meet felt needs of the community - they should solve problems that are apparent to most or all in the community. See below on how those can be met. If that's too abstract, then try, 'What kinds of things, in your extended family, do you tend to worry about?' This will help establish some felt needs, from which