The critical success factors in the client‐consulting relationship
Pourquoi ce travail est dans la base
Une base qui oublie comment elle a trouvé un travail ne peut pas être vérifiée. Voici les voies qui ont admis celui-ci.
Notice bibliographique
Résumé
Purpose The primary intent of this study is to examine recent projects involving external management consultants at a North American telecommunications firm, from the employees’ point of view, to measure the extent to which the aforementioned “critical success factors” were perceived as being evident. A secondary purpose was to examine which, if any, of these factors differ between more or less successful consulting projects with a view to building a model to predict employees’ perceptions of the level of the projects’ success. A third objective was to gather employee opinions on the use of management consultancy and other factors that might contribute to the success of consulting projects. Design/methodology/approach A total of 102 employees responded to a questionnaire consisting of 59 questions. A model including six independent variables was able to predict overall rating of project success, with an adjusted R 2 =0.68, F =27.81 ( p <0.0001). The significant variables, in order of importance, were: the solution took into account one's internal state of readiness; the project included prototyping new solutions; the project deliverables were clear; the consultant partnered with the project team throughout; the consultant was professional; and the consultant understood the sense of urgency. Findings Substantial differences were seen on most measures between projects judged “successful” and projects judged “not successful”. Nevertheless, it is encouraging that many of the success factors suggested in the literature, and proposed under “an ideal client‐consultant engagement”, were judged as being present in management consulting projects at the telecommunications firm, to one degree or another. General opinions of management consultants were mixed and somewhat negative. Employees at the telecommunications organization do not agree with the traditional benefits of management consultants promoted by the industry. Originality/value The results of this study support the anecdotal and theoretical models, in particular those emphasizing the importance of process issues, the client‐consulting relationship and their impact on project outcome.
Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.
Prédiction distillée sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Apprise à partir de 10 348 étiquettes directes de Codex et de 10 348 étiquettes directes de Gemma. Le mode candidate est l'union des têtes enseignantes seuillées; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont ni des étiquettes humaines ni des étiquettes directes de modèles de pointe.
Scores Codex et Gemma par catégorie
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,010 | 0,001 |
| Méta-épidémiologie (sens strict) | 0,000 | 0,000 |
| Méta-épidémiologie (sens large) | 0,000 | 0,000 |
| Bibliométrie | 0,000 | 0,001 |
| Études des sciences et des technologies | 0,001 | 0,000 |
| Communication savante | 0,001 | 0,001 |
| Science ouverte | 0,001 | 0,000 |
| Intégrité de la recherche | 0,000 | 0,000 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,000 | 0,000 |
Scores machine (provisoires)
Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.
Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.
score_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découle