April 29, 2005

technological problems don’t exist

zzzzzz7654221.jpg
Agree/Disagree?

"Hugh's Daily Cartoon" Newsletter. A new cartoon sent out every weekday morning to your inbox [RSS version here.]. A wee chuckle to start your day off right etc.

22 Responses to “technological problems don’t exist”

  1. With tech­no­logy it is pos­si­ble to achieve a lot of inte­res­ting things. But this can take time. And time can be a pro­blem. So yes, tech­no­lo­gi­cal pro­blems do exist. Another pro­blem is the deve­lop­ment and imple­men­ta­tion of tech­no­lo­gies. Peo­ple make mis­ta­kes and there will always be bugs.

  2. Mark Wubben says:

    Well, if there are no tech­ni­cal pro­blems, there are no pro­blems at all. But perhaps you can say that tech­ni­cal pro­blems is too spe­ci­fic, and that they are pro­blems in life? Cul­tu­ral problems?

  3. sig says:

    Ahh, exce­llent brain­tea­ser to get the gray mat­ter wor­king after a nice two hour lunch on Cote d’Azur!
    Yes, tech­no­lo­gi­cal pro­blems exist if you’re lazy.
    No, they can be made to disap­pear by cha­llen­ging the assump­tions, never taking the ori­gi­nal ‘pro­blem’ at face value.
    Say you told me you wan­ted a “car to take you from Paris to Ber­lin in two hours” (that’s 1052 km, mostly motor­way though, some traf­fic, some radar traps).
    Take pro­blem as sta­ted: Huge pro­blem, tech­no­lo­gi­cal and other­wise.
    Fuck the assump­tions: “Why car?” -> shrug of shoul­ders -> “Call Air France!” No pro­blem.
    alter­na­ti­vely,
    “Why two hours?” -> “Dri­ving is boring!” -> “Here are the keys to Hugh’s Ferrari Spy­der and a nice lunch ham­per, enjoy!” No pro­blem.
    In exten­sis it could be applied to anything. Just apply “no limits” to your ima­gi­na­tion :-)

  4. Ric says:

    Cri­key, Hugh — slow down! I thought I’d caught up with you, but I’ve been over at Sig’s and come back and find you’re still at it — this being on the other side of the world can be a pain (as he sli­des into fit­ful sleep at the key­board …)
    Sig (pre­vious com­ment) notes something very fami­liar to me — often peo­ple phrase their pro­blem in terms of a poten­tial solu­tion, uncons­ciously narro­wing their view. Reph­rase the pro­blem correctly, and other pos­si­bi­li­ties become more easily appa­rent.
    As for tech­no­lo­gi­cal pro­blems (and this is, I think, the ques­tion you were really asking) — are not the pro­blems more to do with peo­ple (e.g. cul­tu­ral) than with tech­no­logy? Was it Jules Verne who said that if you (a per­son) can ima­gine it then it will even­tually come into exis­tence? Lon­ger term I don’t think there are tech­no­lo­gi­cal pro­blems, only pro­blems that we (the peo­ple) have with the technology.

  5. brian says:

    tal­king (typing) out loud here — don’t expect cohe­rent thought pro­cess..
    Tech­ni­cal know­ledge and tech­no­logy is essen­tially about expan­ding a sphere of con­tol over a pro­cess or object. It is also about making that con­trol repea­ta­ble and kno­wa­ble and trans­mi­ta­ble to others without a direct rela­tionship. Write the manual, pass it along. You want the ans­wers it’s in the book.
    Tech­no­lo­gi­cal pro­blems exist to the extent that the sys­tem of con­trol encoun­ters something outside of it’s sphere of con­trol — it then become a pro­blem — which the tech­no­lo­gi­cally min­ded imme­dia­tely looks for a new tech­ni­cal adap­tion or inven­tion to then bring into the current control/technical con­tol sys­tem.
    This I think con­trasts with cul­ture, which isn’t about tech­ni­cal solu­tions but balance bet­ween various inte­rests and know­ledge bases. Cul­ture is also an sys­tem of con­tro­lling the envirn­ment, but not through pro­cess but through rela­tionships.
    At a base level the technological/cultural ques­tion is the same thing — con­trol of the envi­ron­ment and of the direc­tion in time of the aims of that con­trol.
    Growth of tech­no­lo­gi­cal sys­tems reach a point of “loc­kout”, when deve­lop­ment of the current sys­tem of con­trol make in inhe­rently almost impos­si­ble to read­just to another tech­ni­cal sys­tem because of the sheer weight and expense put into the current one. So any teh­ni­cal ans­wer will the­re­fore create it’s own pro­blem even­tually.
    For­get IT for a second and think of, I don’t know..martial arts. Someone deve­lops a tech­ni­que for kic­king really well. He impres­ses peo­ple and his stu­dents codify what he does and make it a method — a tech­no­logy of figh­ting. And ever­yone gets really good at kic­king well. They think they are invin­cia­ble. Kic­king is the ans­wer to everything, and becaus eof the tech­no­logy of this style you expend lots of energy lear­ning how tro kick accor­ding to this method. One day our invin­ci­ble kic­kers meet a really good wrest­ler who nega­tes everything they can do with ease and gives ‘em a good bea­ting. What do the kic­kers do? — Say “Hey, that guy didn’t kick — unfair!” (ignore pro­blem, blame someone else, outside of sys­tem of tech­ni­cal con­trol so can’t unders­tand pro­blem), “Our kicks were use­less!” (either rein­vent how to kick in light of new know­ledge form encoun­ter with wrest­ler; or give up kicks as a tech­ni­que because they are now dee­med “worthless”?)..lots of ana­lo­gies here..
    OK going to stop thin­king out loud..technological pro­blems do exist, but they coem from the tech­no­logy themselves…

  6. I’d say, of course there are tech­no­lo­gi­cal pro­blems. But they’re not *the* pro­blems. Those are social, men­tal. I’ve been inte­res­ted in organization/categorization (of everything; ideas, things, peo­ple) for a while. The pro­blem has not been tech­no­logy — though there’s plenty of work to be done there — ins­tead *the pro­blem* is get­ting peo­ple to stop focu­sing on strictly hie­rarchi­cal struc­tu­res.
    That’s just one exam­ple. Tech­no­logy will come to be adop­ted, but only if the social, men­tal blocks come down first.
    An aside: peo­ple seem to asso­ciate “tech­no­logy”, the phrase with new/digital. That’s just silly. A ham­mer is tech­no­logy. Ditto paper. Ditto forks.
    So, if peo­ple think you can’t eat with anything but chops­ticks, your fin­gers or a spoon, then deve­lo­ping a bet­ter uten­sil is not a tech­no­lo­gi­cal problem(/solution). The real pro­blem is get­ting peo­ple to see that there may be a bet­ter way to eat is the pro­blem. And as Gald­well preaches, this is hardly ever something that inno­va­tors can accom­plish. It’s the connector-mavens that do this.
    i.e. Tech­no­lo­gi­cal pro­blems are hardly ever only so. This why having a good idea, good pro­duct, wha­te­ver, is just not enough. You have to find the underl­ying social pro­blem and talk in its terms. The tech­no­lo­gi­cal pro­blem will be easy in comparison.

  7. mike dunn says:

    agree…
    there are always tech­no­lo­gi­cal “cha­llen­ges” — that is the fun part…
    there are always reli­gions of tech­no­logy “pro­blems” — that is the not fun part…
    tech­no­lo­gi­cal agnos­tism (right tool/right way/right solu­tion) is the cure that helps address both — imho :)

  8. Tech­no­lo­gi­cal pro­blems exist, but they should be irre­le­vant to ever­yone other than the buil­ders of tech­no­logy. They become rele­vant to other peo­ple, when a piece of tech­no­logy falls just short of sol­ving a real pro­blem they have. If some wid­get sol­ves a pro­blem for someone, then that per­son has no tech­no­lo­gi­cal pro­blems with the wid­get. If wid­get doesn’t solve the pro­blem at all then there still isn’t a tech­no­lo­gi­cal pro­blem: the per­son doesn’t use the wid­get. Tech­no­lo­gi­cal pro­blems mani­fest when the wid­get almost sol­ves the problem.

  9. sayten says:

    Tech­no­lo­gi­cal pro­blems do exist. My view may be tain­ted since I’m a tech­ni­cal guy who works in the trenches. The suits are the ones who’s ans­wer to this ques­tion really mat­ters.
    I like what Sig said about other options but I think that lazy is a strong word. If the pro­blem is get­ting from point A to B then maybe there are 3 or 4 ways to do that but there are times when thro­wing out assump­tions does you no good. Some­ti­mes the tech­no­logy may not exist to exe­cute a task within the cons­traints of the job.
    I can ima­gine a day when we have wire­less power but that doesn’t mean I can stop char­ging the bat­tery in my cell phone right now.

  10. pheloxi says:

    tech­no­logy is as smart as its user.
    if you try to use techo­logy above your know­legde the chance you will get errors is high, because techo­logy itself has no knowlwgde. a user who will inc­rease the know­legde will get smar­ter. the lear­ned know­legde will than make user smar­ter, but also the tech­no­logy, because the user can be more advan­ced.
    1 + 1 = 2
    1 + 1 = 5 — 3

  11. Ken Dyck says:

    Sorry Hugh, I have to disa­gree with you here. Tech­ni­cal pro­blems exist.
    I think what you are get­ting at is that all pro­blems arise from basic human desi­res that usually have little to do with tech­no­logy.
    Let’s say you’d like to walk on the sur­face of Mars. There are many defi­nite tech­ni­cal pro­blems that need to be over­come to ful­fill that desire, such as kee­ping a per­son alive in a spa­cec­raft long enough to sur­vive the trip, pro­pe­lling the vehicle to its des­ti­na­tion, and lan­ding it on the sur­face.
    There are also defi­nite poli­ti­cal and cul­tu­ral pro­blems. You must, among other things, con­vince some­body or orga­ni­za­tion with the means to send you to Mars to do it, for exam­ple.
    Both types, tech­no­lo­gi­cal and cul­tu­ral, are real pro­blems. Your desire to walk on Mars is, howe­ver, all yours.

  12. Carl says:

    Tech­ni­cal pro­blems most cer­tainly exist, and they can deter­mine what kind of cul­ture deve­lo­pes, too.
    As an exam­ple, Live Jour­nal ( http://www.livejournal.com/ ) allow “friends’ lists”, which gives you a page to moni­tor all your friends’ jour­nals, (not to men­tion RSS feeds). This means you should notice all your friends’ posts without nee­ding to go to their journal’s. You can also receive email-alerts when you get replies to your jour­nal, as well as replies to any replies you’ve made in other jour­nals.
    Full-featured you might think, except that for­mat more or less ensu­res threads on a topic will peter out within a day or two — unless two or more peo­ple keep end­lessly repl­ying to each other.
    The result is mostly off-the-top-of-my-head dis­cus­sions, rather than ones made up of thoughts that’ve been mulled over for a day or two.
    So, on Live Jour­nal, the cul­ture is mol­ded by the tech­no­logy, and if you con­si­der dis­cus­sions ending in a day or two to be a pro­blem, then it has a pro­blem — one that’s enti­rely due to its tech­no­logy. (Sim­ple email lists are an exam­ple of a tech­no­logy without this pro­blem — every­body on the list gets every post and every reply.)

  13. Malcolm Ryder says:

    I’ll grab the invi­ta­tion to spin the open ques­tion… sure there are tech­no­lo­gi­cal pro­blems, mea­ning that there are pro­blems crea­ted by tech­no­logy, and/or mea­ning that there are situa­tions in which tech­no­lo­gi­cal approaches to solu­tions are con­si­de­red to be either the acce­le­ra­tor of the solu­tion or the inhi­bi­tor!
    I’ll also volun­teer that “tech­ni­cal” and “tech­no­lo­gi­cal” are not the same thing, and as soon as we stress the “-logi­cal” we’re moving in on the aspect that points more at deci­sions to use the tool than at the tool itself. The deci­sion to use the tool might be vali­da­ted or might be corrup­ted by the cha­rac­te­ris­tics of the tool itself.
    I’d say a tech­no­lo­gi­cal pro­blem that we all know about is the situa­tion in which we work to try to adapt (by con­fi­gu­ra­tion and/or by usage) the tool to the cha­rac­te­ris­tics that we think the *solu­tion* should have. How do we go about deci­ding that a tool fits the cha­rac­te­ris­tics? The big­gest mis­take we might make is in thin­king that the tool *is* the solu­tion, ins­tead of thin­king that the tool can *sup­port* the solu­tion. When we make that mis­take, we usually shrink the pro­blem to the shape of the tool, ris­king put­ting the cart in front of the horse. But sure, it’s also pos­si­ble to have a pro­blem for which the solu­tion really nee­ded is to have a tool ins­tead of not having one! There are plenty of those pro­blems to go around. Ask any designer…

  14. Keith Handy says:

    Hugh: is the sta­te­ment in ques­tion an actual obser­va­tion that you had, or just a CCC — cal­cu­la­ted con­tro­versy catalyst?

  15. hugh macleod says:

    What, Keith, are those the only two options I’m allo­wed? ;-)

  16. Bill de hOra says:

    Tech­no­lo­gi­cal solu­tions don’t exist.
    Agree/Disagree?

  17. Bob McCabe says:

    There are no tech­ni­cal pro­blems, only the fai­lure of mana­ge­ment to expect that there will be techin­cal problems.

  18. MarkN says:

    Tech­no­lo­gi­cal pro­blems will always exists because “sol­ving the pro­blem” stops the ins­tant the mar­gi­nal bene­fit falls below that of some other grea­ter institutional/organizational/personal need.

  19. Ben says:

    Re tech­ni­cal vs tech­no­lo­gi­cal. I agree they are dif­fe­rent. My take:
    Tech­ni­cal rela­tes to tech­ni­ques & tricky­ness. Tech­ni­cal pro­blems are pro­blems that go beyond the sim­plis­tic, and require some appli­ca­tion of thought and tech­ni­que to solve. Tech­ni­cal pro­blems DO exist, but are rarely impos­si­ble to solve, espe­cially if one thinks outside the square.
    Tech­no­lo­gi­cal pro­blems relate to tech­no­logy. As ever­yone else hin­ted, genuine tech­no­lo­gi­cal pro­blems only exist if the sol­ver has a blin­ke­red world-view. Sure it can cost a lot to solve a tech­no­lo­gi­cal pro­blem, but they can always be sol­ved. In my world (soft­ware deve­lop­ment) ‘unsol­va­ble’ tech­ni­cal pro­blems usually come down to a poorly defi­ned scope and a reluc­tance to pony up the time (and the­re­fore money) to do something correctly with the most appro­priate* tech­no­logy.
    *Or pre­se­lec­ting a tech­no­logy (Mic­ro­soft) based on unrea­so­na­ble bias (cor­po­rate policy).

  20. Ben says:

    Re-reading my com­ment, I think I just rea­li­sed what Hugh is get­ting at:
    »> Tech­no­lo­gi­cal pro­blems do not exist, cul­tu­ral pro­blems do.
    Too many times in my industry (which pro­vi­des ser­vi­ces to EVERY industry) we are stum­ped by tech­no­lo­gi­cal pro­blems crea­ted because of the customer’s cul­ture. When a pro­blem would be sol­ved by an ASP.NET solu­tion, we get told “no, sorry, we’re a Mac house”. When a pro­blem could be sol­ved by Java, we get the “no, sorry, we only use Com­paq hard­ware run­ning Mic­ro­soft”.
    Or maybe I’m loo­king at it too tech­no­lo­gi­cally? :)

  21. mike dunn says:

    right ben, exactly :)

  22. Dre says:

    Agree! pro­blems are just psycho­lo­gi­cal. Even worse… define “pro­blem”! :)