Vous êtes sur la page 1sur 24
«2 United States Patent Alleman et al. {US007110988B1 US 7,110,988 B1 Sep. 19, 2006 (10) Patent No. 4s) Date of Patent (S4)_ AUTOMATED SYSTEM AND METHOD FOR CREATING ALIGNED GOALS (75) Inventors: Andrew W. Allemann, Austin, TX (US); Shad W. Reynolds, Austin, TX (US); Adam R. Hunter, Austin, TX (US): Justin B. Petro, Austin, TX (US) (73) Assignee: “Trilogy Development Group, Ine, Austin, TX (US) (*) Notice: Subject aay dislsimer, the term ofthis. patent is extended or adjusted under 35 USC, 1540) by 585 days. 21). Appl. No: a9920,488 (22) Filed: Aug. 1, 2001 (51) Int. C1, GO6E 15718 (2006.01) 6066 700 (2006.01) (2) US.CL «O67, 706°; 7064; 700/50; “70\/40; 701/57; TOL98 (58) Fleld of Clusiieation Search 70518, ‘OS/7; 7067; 273/400, 473/871, 478 ‘See application file for complete seach histor: 66) References Cited US, PATENT DOCUMENTS 5548506 A+ 81996. Srinivasan 088 SSI9.263 A * 101998 Bromley aa. 7073 6330872 BI® 122001 Sika Sor 208 200210038500 Al® Yoo eal 7089 20020173999 AL® Grif et 7087 2on21oas Al Sulivan 7088 20030229829 ale Mui ea. 088 doovor7am20 ale Spelinan eta. 7088 OTHER PUBLICATIONS. Lowry tal; Organisational charters, cultural qualities and cacellence in leading Austalian-oned information technology fms Information Systoms Coafrece of New Zealand Poceade ings; Oct. 3-31, 1996; pp. 72-84 Boardman «al Integrated process improvement in design and ‘manufictre using a systems approach; IEE Procsedings-Contl ‘Theory and. Applicaton; vol. 143, 6 2; Ma 1996; pp. 17I-I8S.* Jivison; Software project management the manages view; Com- nications of he AIS: No 1999.2 ‘Begsman ca Session suppoting face-to-face groups: Project. ‘Niek: meeting aymenaton and analysis Procedngs othe 1985. ACM conference on Computer-suportel cooperative work; Dee 1986 Payne e al; Demonstration: persusive agents and architectures: ‘Agenc-based support for hunaw/ageat teams; CHE ‘00 extenied alstracts on Huan fictors in computing stems; Ap 200° (Continued) Primary Examiner Anthony Kaight Assistant Examiner—Ronald B. Williams, J on ABSTRACT Amethod of aligning anew gol of an entity ensues thatthe ‘ew goa i a child goal ofa pareat goal, The method also ‘ensures that a group i inked tothe parent goal, and ensures tat the entity is subordinate tothe group. In one embod ‘ment, selection lists constrain the available values forthe goup andlor the parent goal In another aspect, 2 method of facilitating contextalsligament of anew goal recognizes an ‘organizational role for an entity and customizes conteat of user interioe, based onthe organizational role ofthe eat. ‘The user interface wit the customized content provides goal creation guidance according to the organizational role. Ia ‘one embodiment, the customized content includes special- ined insiretions and sample content for characteristics of the new goal, such as a goal-objective characteristic, a goal-measure characteris, and a goul-activily charactris- ti 38 Claims, 14 Drawing Sheets US 7,110,988 BI Page 2 OTHER PUBLICATIONS (Chur tal; Tols to algn goals and infomation items; IEEE. Software: vl. 12, 1s. 3; May 1998; pp 108-109 (nas, Defining goal-diven fault managemet mts in a eal word envionment a easetaly’ from Nok: Procelings of the Fourth European Software Maintenance and Recaginecring, Fe, 28-Mar. 3.2000; pp 10-107 asseius ct al: The interactive goa pane: a methodology for aligning RAD activities with corporate sateyy neratioal Con. ference on Engnesing and Technology Management Proesings; (Oct-13, 1985 pp. H247-* lectonie Brochure ened “A Quanitaive Leadership Tool for Performance Management” obtained from “Peformance Woikbench” (TM) ypesiak on webpage at , Prin Feb, 6, 2001 ‘Webpage for Pesfomaworks-Pefomaworks Soin Products at ep ww peformworks com performaworks Sltion pred- ‘uss nl, Prntod Fb. 6, 2001 * cited by examiner US 7,110,988 B1 Sheet 1 of 14 Sep. 19, 2006 USS. Patent G08 EENHO 030 SINS staHo dog ‘SHIA WAL WvOV 350 (GNon) -INSe¥E 030 | U.S. Patent Sep. 19, 2006 Sheet 2 of 14 US 7,110,988 B1 FIG. 4 7 GOAL MANAGEMENT SYSTEM _ ae 18~J DATABASE 18 19] cuent I ye] SOMO Locie 0-11 ALIGNMENT ROLL~UP TOTAL CUSTOMER SUCCESS FIG. 16 190-4 QUALITY COMPLETENESS |GRAY-NO NEED TO CHECK ALIGNMENT US 7,110,988 B1 Sheet 3 of 14 Sep. 19, 2006 USS. Patent “WOINKSL BBUHL Va CCE (NON) :3ENMO AVAL 3Av0 :33NNO HUNOYS “WNOSMzd “SAWN ouio ORG WEL § 91a Wd SENKO 7 1ondoud SAWN ‘Naa TAO Z LONdOed pomoda NI s3unwvad @auino3e | SoadS TW ‘Tv ININTANt “AIO SIBW IVHL SAL Wd 1 304030 7 sondoud 3 ————— NON) SERIO Wal aqaoT=NGG Londoyg| —_ | SSF WH vd 33N00 “3AV0 3U3NWO AVL ++] ‘3Av0 ‘SNM ‘SS3NBIZTANOD “JAVA 3Av0 “S3NKO 1 faneons ZALFWND ZING + —+| ALTO SRN al ‘SSIOONS YINOLSND amy ‘Wik ‘INBVd |_ 03 | aAva ISIAH! 808 X00 ‘SHaeRGW WSL WOv lt INvOW :33NMO ‘way > sy00g ano; || Aipuuung 3A, zoL eayory J] swoe; J] eidosa J] sioo9 a] dung yoind soinpon. 42 sequioroy “opsoupsn AY DALU0D@S|DOD, 005 (90607 diay _woypujstuqmpy —junozay snoy _ewoH woo'dh jap0e7 US 7,110,988 B1 Sheet 6 of 14 Sep. 19, 2006 USS. Patent £ OLE jpbey A6oin] yoDqpe0 se = dos of onujusg | “spoou oyjpeds anok yns 0} Au060j5 oy 6 efuoys how mo, -uesooys @A,nok 2 tBop s,woay sui Aq poumneiee TT ‘aud 51 Al0B9j09 1006 ey), ‘HioB9459 1809 50049 “SenjOA pud ss pup 9jop 0} dn uw, eins expu “sjuena A '8q Of 9|gOII0AD sjasku exoW SKOmIY peeled p04 eo = | Yai085 sayouo}ny ‘Guys Aow nok yBnoup ‘Aoyuy uy 485 SDM S14, -0} 1005 [Thos poten gue) T dieH 499, p09 KEN D 908i < 51009 270 PS juewubiy [Peo AON — Z dels 309 ane) senasiq PJDZIM [DOD MAN Y 8}DAlQ S009 ino, ewop>> Tiowuing n04 sip09 ‘si06g [Eq dune eind_seinpon ‘yoG07 dey voy qunossy ano, ewoH US 7,110,988 B1 Sheet 7 of 14 Sep. 19, 2006 USS. Patent 8 Old 909p20 9 Tobey Abou, vsunok 4 exDu p08 D as004> ui 0, nok Moo nok yuosoid -M si009 yoo19 yBnoy} nok poo) qaubes eno F ‘suoewWos Jo [Dob 201d ‘|poB Mau puoIg D BuyDalo 2i,nok 41 aidoad ows d19H 199, [P09 Ko D 0jD010 of pADZIM 1009 ou} esp 08 Buyjsjxe uD AyIpow 0} esooyy 1009 Suyspg 40 MON — § Geis abe9 ino], FeAOeID $1009 nO ‘Sen08g [P09 |DUOSJeg D efDaIQ ewioH>> ‘eauaay sjp09 [Eder y21m9 someon wretoy dey doy julwpy yunocoy ano, @uloy) US 7,110,988 B1 Sheet 8 of 14 Sep. 19, 2006 USS. Patent [ebay Aeon, Pasion Jom pud onjoauy 2q 04 oid 60168 Deans zat 140 1 860g uy UW, eins eyolu “siuene ‘jeskus exw SAOKIY 40 oBojusa10d x jo Suneey mm ss61603¢ ng Auuyor 0217 sseB0U0H, anyououny un sseuisng Yuwis 90p :SW0N, dey 129. 180 WON © 90819 < 51009 an, HPS $1009 anOA SENOS eyoosy flips _Js28g PudzZIM 1D09 MON D ejDe1D ‘woy>> 009 an, Tiouiuing ane 51005 [Eq curr ain seinpon 0057 doy uoyouruwpy —junoaay_anay ou IZ sequeroy “opsevpen {UDALUO@S|D0D Woo-dyssopoe7 | US 7,110,988 B1 Sheet 9 of 14 Sep. 19, 2006 USS. Patent ea] Moya “sonjpA pup sseujenq = AB0]uy e7OU “sjuore Guynuoed’ uy paron o0foig pu0g yuowidojonog enjowoyny (>| “senjox puo ssousnq si soy, | OOH “HOH BuTIPE wy poHon wauubyy | 1608 sh x Jo youd ssou6 0 aaDs so jJem $0 ‘99z 0} @BDIeAD yjoq AO 3m UD ejOp 0} dn wi) eins IDYOAD jJashy exoW ShOMY 10°L0°90 (ups) sewyey “u 6) Muon ey Jo sbojussied “09Z$ 4 1DU 111g @BoueAY OL (wpa) poaPORTe den 9 9 dis of anutuod [~ ge) 4) -aBunys of 1S 0} pavaoid nok 404} 6910 ot [P09 ABN © BIDBID < 1069 30K IPI 300 InoA ssn 08g Sareea {909 we] D 94Del) ewoH>> [sue J erdood J|_sivo9 51009 ano, ‘Towing ano, EL WZ sequin “KopssuPeR AUDA LUOD®@S|DO9, 1Fobo7 Gipy_ vayoASIUUPY jnoDDy Ina, eu wos dyyssepoe US 7,110,988 B1 Sheet 10 of 14 Sep. 19, 2006 USS. Patent spogpee se loor'so:pug Apo uj Aonb ‘eyy 40 eBojusored X Jo yosd ss0i8 0 eADs so jI9m SD ‘09z 0} @BDI0AD Uy sBoiony “097s 40 9404 I web Sie 4#9 1009 MeN © 64089 < $1009 JH, UPS ‘yee9"inoy ssnosi0 | Too8 seuoUO BPY TA zej noyros kow no, -wiojshs j006 ou of I $S@3B034 jouosieg Jujuy PPY - 9 dais pence] tsoa co ioet fora 1009 an, Gowns ane, syo89 were AD PIOZIN 1009 MEN D 1081). wdosd J_si909 = suoK>> Coton JL awe 12 sequoroy “lopseupen AUDA WUOD@S|009 || yunoooy ano, awoy US 7,110,988 B1 Sheet 11 of 14 Sep. 19, 2006 USS. Patent gl ‘ola a (p67 Bor Wooqpen je edxe | JOYA ,,pUOEq PUD eAogD seOb,, {Dy ‘unspeu! 04} si‘jo05 0 30 juewele yo}eujs oy] “aq jySqu ojduioxo uy 2140 sjonjoxo ups JeBDuDUU nok yous US SIY] “JOOB ay Jo jusWlels jond © 8q PINOYs [008 D Jo suNsooW oY dia 49 009 MON © 60819 < WaIeIS puD “elnsDey ‘31009 ano, SsnsIq $1009 ano, ‘rowuing ano ‘1009 BIOTIN 1005 WON Y IDEN ciao i009, dumnp_ 991N0) So)npOK jweron “Aopssupen AYDALUOJ@S|DOD jwpy _junoooy ano, awoH ‘wioo'diyssepoe7 wotey dey ve US 7,110,988 B1 Sheet 12 of 14 Sep. 19, 2006 USS. Patent EL ‘O1L Oe weGey Abo 790qp0030 vl ‘Buyyp3 1009 ysIuLy Auauoy_PPY P 0} D $0 e60d Arpumung uo nok 40} pefoidsip exo S24.A420 sno, "|008 amok ysyduioa00 9} HY I,nok syafoid judpoduu, Ayan ai a ae ae Sosayoy O09 MEN — S dais “#1609 Inoj_ e8nB5Ig PADZIM [DOD MBN ¥ 2j0819 ~_sY99 a0, owoH>> “Gowns 7964] 81009, 3909 aT dune 51 _s2INPON 70807 dio 3y_junedey ane, alo 17 sequsron “opsouren KuDdU0J@S|D09 | 7 ‘ios diysiepoey US 7,110,988 B1 Sheet 13 of 14 Sep. 19, 2006 USS. Patent A601 0557 yeoqpeeye “Hf 0} UbYo 0} wiO9} anof si asj0 Wm 41 4nq ‘sunNok wowaL |IAA [Oo6 oy“ nok 40} s|008 umo snok yo -sonyor pup ssouysng s AB0)L Pup 9jop oj dn wi) uns ayo UL PaAjoaul oq of ajgoyoAo sjoskus oyOW SkOAIY O “u Bp] Auonb ous 40 e6oyuoaied x Jo yyoud ssos6 80 ‘097 9} @BbieAD Yjoq AO “O9Z$ OF 9404 II1q eBoIeAY syE AON p09 woe) D s}006 snok Jo auo 9404 WA wD2} amok 40} oy0W Nok 106 Auy “say peaooid *}008 ‘Mou pupsq 0 Guyjoas0 eu nok 4) Yyo}D49g wos J009 MeN P epDe19 die 169 109 REND e408 < Si009 304 HPI 51009 sno, Ssnosiq 31009 2904 Rousing ano, | ‘009 |D09 We] D ejDelD wioH>> s1p09 Iz saqueien “emsoupen AuDdUO@S|DO9 wipy _qunoooy ane, _eOH woordlyssopOeT OAUONY dun 210 SANPON jnobo7 djeH u US 7,110,988 B1 Sheet 14 of 14 Sep. 19, 2006 USS. Patent pba] _ Abaya “speed oyjoeds anok yns of MuoBejoo ey ‘Bunya Aow no, “ussooys 9a,n0h Ipo9 s,uioe) sy Aq poujuudjep feud 51 KoBajoo jo08 oy sku yD shomy ‘u 60} Ayonb ey Jo eBojuecsed ypelo1g poy X 40 youd ss018 0 aos so jJoM $0 ‘097 0} @BDIeKD UIC *AOH juatsdoyeroq “09Z$ 9} 9}04 I11q eBoveAY oY) eAON $1009 s,uiDa1 4o0fo1g pioj upuoiny “wooy yueuind ey Jo shou juoind p eq jsnu) woo} oy) *0} jD08 [Cum reg per] ou ID 0} wday o Joos — 091 LAL_woel Weloud prod yusuuBiy queuing 10} UBD 0} woe] es004D IUD ss61601q TwowUbly 1009 MON — eg ypoqpee se Sota 940019 [009 wa, MeN Y 9}Da19 ewioH>> i009 ano, Tiouuing ano, sipo9 31009 wob07 dian sluwpy _yunoo9y ano, awoH ‘topseupeh KuDdWOD@S|D09 woo"diyssepoe7 US 7,110,988 BI 1 AUTOMATED SYSTEM AND METHOD FOR ‘CROSS REFERENCE TO RELATED "APPLICATIONS. s This application i related to U.S. patent application Ser. 'No, 09/895,488, entitled AUTOMATED SYSTEM AND. METHOD FOR MANAGING GOALS, fled on Jun, 29, 2001, (hereinafter, the 0109 Applicaton). The 0109 Appl cation is hereby incorporated herein by reference. ‘TECHNICAL FIELD OF THE INVENTION ‘This inveation relates in general to the field of data processing. More specifically, this invention relates to an Automated system and method for eweating aligned goals. BACKGROUND OF THE INVENTION A typical lage business onganization inludes numerous twams of people, with one or more specifi tasks assigned to cach of the teams. A traditional business tends to define its teams in terms of the business’ chain of command (i. the reporting chain), For example, a typical business sales» vision has a numberof sales teams, each led by a manager who reports to a vioe president of sales. In this type of chain-cf-command structure, members of a sales team are “direct reports” of their manager. Other members of the ‘organization typically aust coordinate ativities with a sles ‘eam member through that member's reporting structure. An entity such as business organization thus typically includes ‘numerous subsidiary enttes such as teams and individual, and some of those entities are subordinate to others, accord {ng tothe command chain oF according to other relationship rules. Companies generally ideaify certain strategic and tactical goals, which they believe will lead the company’ to succes, Specifically, managers typically establish goals for their ‘porting units, and employees are also often encouraged to sot personal goals Recently, business leaders have come to recognize a ‘number of advantages associated with adopting more flex ile stategies for organizing teams and setting goals to supplement the igi, hierarchical reporting strtures tra tionally found in large organizations, For example, raher than requiring all eam members to have the same supersi- sor, more flexible strategy allows atleast some teams to include members from different levels of a reporting chain ‘andor fro diferent reporting chains. Teams with members from different reporting chains are considered eoss-fune- ‘ional teams. For instance, sales manager may be assigned to a product development team charged with ereating a salable product. Such a cross-functional team increases the likelihood that a developed product will be commercially ss viable ‘Similarly, another exible strategy for organizing teams and seting goals allows team leaders to set team goals but doesnot require sect adherence to a conventional reporting chain when choosing team leaders. By adopting flexible ands éynamic strategies for managing teams and goals, organi- zations facilitate more rapid and effective adapation to changes in the business environment, provided that those strategies are well implemented. ‘A disadvantage associated with flexible and dynamic strategies for organizing teams and goals, however, i th such strategies typically result i team and goal structures 8 s 2 with increased complexity, compared to traditional chain- cof-command strategies for managing teams and goals. For ‘example, effective personal goals align with team goals and ‘organization-wide goals. na flexible and dynamic environ- ‘ment, however, onganization-wide, team, and personal goals are rely sai as company objectives, products, personnel responsibilities, and personne team memberships may Ire- quently change in response to changing conditions in a realistic business environment. Flexible and dynamic strategies for mansging teams and goals ae therefore typically much more dificult to imple- ‘ment. Although conventional management information sys tems (MISs) may provide basic functionality for storing state goals, conventional MISs generally lack facilities for ‘overcoming the dificulies associated with flexible and dynamic strategies for managing teams and goals ‘SUMMARY OF THE INVENTION The present invention relates oa method, a program product, and a system for guiding a goal creation process according 1 approves relationships amoag_goals and ‘between goals nd entities such as teams and individuals One embodiment of the present invention relates to a ‘method of aligning a new goal of an entity. That method ensures thatthe new goal sa child goal of parent goal. The ‘method also ensures that a group is inked othe parent goa, ‘and the method ensures thatthe entity is subordinate tothe soup. For instance, selection lists may be used to constrain, the available values forthe group andor the pareat gol Another embodiment involves a method of facilitating contextual alignment of a new goal. Tha method recognizes an onganizational role for an entity and customizes content of a user interface, based oa the organizational role ofthe catty, The user interface with the customized coatent pro- vides goal creation guidance according othe organizational role, For example, the customized content may include specialized insiactions and sample content for chaactris- ties ofthe new goal, such as a goal-objective characteristic, 4 goal-messure characters, and a goal-octivty character: istic ‘The embodiments summarized above thus facilitate the creation of goals with proper alignment, acconding to rules in an organization defining approved relationships between things such as goals, teams, and individuals. Additional ‘embodiments provide additonal technological solutions for guiding the goal eration process. BRIEF DESCRIPTION OF THE DRAWINGS re complete understanding ofthe iaveation and its objectives and advantages may’ be acquired by referring to the following description and the accompanying drawings, wherein: FIG. 1 preseas a table with two columns respectively depicting a static chain of teams and a dynamic chain of teams, with arrows highlighting some differences between the static and dynamic chains; FIG. is. bloc diagram depicting relationships between goals, teams, and individuals: FIG, isa block diagram depicting relationships between individuals, teams, and various types of goals: FIG, 4 is a block diagram of the physical and logical components of an example goal management system; FIG. § presents a flow chart depicting a process for creating goals according to the example goal management system: US 7,110,988 BI 3 FIGS. 6-8 depict example user interfaces fr initiating 3 goal eration process; FIG. 9 depicts an example ser interface for retrieving an existing goal tobe copied into a new goal FIG. 10 depicts an example use interface for modifying the new goal, FIG. 11 depicts an example user interface which indicates that the new goal has been saved: FIGS. 12 and 13 depict example user interfaces which ‘cept contet for the new goal FIGS. 14 and 18 depict alternative user interfaces for initiating a goal ereaton process; and FIG. 16 depicts an example user interface that provides alignment information fora chain of goals. DETAILED DESCRIPTION Overview ‘The difficulties associated with supporting exible strat- egies for team and goal managemeat include challenges relating to ensuring that pools are organized in a logical and ‘sof way. For example, in an organization with hirarchi- cal teams, it is generally preferable forthe goals of the vo lowerevel teams 1o be aligned with the goals of the higher-level teams. That is, lower-level or secondary goals, should generally align with higher-level oe primary goals However, when an organization allows teams to be ona. nized according to two or more different hierarchies, it is dificult to provide Hexibilty with regard to relationships between goals, teams, and individuals, while ensuing that ‘ew goals align properly with existing goals and teams. In general, a secondary goal is considered tobe “aligned” ‘rin alignment” with a primary goal ithe secondary goal assists in the realization of the primary goal, For example, ith reference o FIG. 3, the secondary goal of implement. ing al roquired features in software Product Z. is aligned ‘with th primary goal of producing software that meets all specs. Additional advantages ae associated with goa! manage ‘ment strategies which use two or more different types of soals to differentiate between goals for an entire team (i ‘wam goals) and goals for individual team members, suchas teamrelated goals. However, such strategies. furher increase the difcuty associated with ensuring that new goals are properly aligned. For all of the above reasons, ‘organizations with flexible team and goal management strat- egies generally face greater risks of goa! misalignment “Therefore, a ced has arisen for methods and systems for uiding the goal creation process to ensure tht goals are properly aligned. For example, a noed exists for methods and systems which ensure that team goals are fnked to appropriate teams. furher noed exists for methods and systems which guide goal creation by customizing content for one or tore goul-cration user interfaces, based on the ‘organizational role or job tile ofthe individual ereting the ew goal ‘As summarized above and described in greater detail below, an embodiment of the present invention guides an individual creating a new goal to easue alignment of the ‘new goal The embodiment accomplishes that objective by ensuring that proper relationships exist between the nev goal and a parent goal, and between the parent goal and a ‘eam, For example, the embodiment ensures that team goal is creatod only by the individual who owns the associated team, 8 % « 4 Another embodiment customizes content for one more sgoal-creation user interfaces, based on the organizational role o job tite of the individual creating the new goal. For example, if he individoa i a manager of product develop ‘ment, the customized content may include instractions relat- ing 1, and sample content derived Irom, a predetermined {pial goal for managers of product development ‘An example embodiment implements technologies for ‘guiding the goal creation process as components ofa goal ‘management system or application. The goal management application may operate on computer or network of ‘computes EXAMPLE EMBODIMENTS, Refering now to FIG. 4, gol management system 10 is an example of a system that provides the technological ability to guide the cretion of goals rom the personal evel to the highest company stateuc initiative. Goal manage- ‘ment system 10 has application toa wide range of industries and otberongnizatons where goals and alignment of pels an be important, Example benliciry industies include computer harlare and software, profesional serves, financial seviees, automotive elecommunicatons, mesial an pharmaceutical, and construction. (Goal management system 10 uses two basi team type sutc teams and dynamic teams, The sai teams depict the reporting chain of an organization and coerespond, for example, to the management seucture reson in the Om- rizaton’s human resources (HR) database, Specifically, FIG. 1 inctodes a et column tat lists Aeme's static teams ad ight column ht lists Acme's dynamic teams, where ‘Acme isan example owanization. Te static teams core- spond the Acme reporting chi Gol management system 10 implements tum manoge- ‘ment rules, sch a the rules desea in the 0108 Appl cation, to ensure that te stored stati teams aze organized according to the roporting chain. For instance, in the cxample embodiment, the rules require every static tam to have one owner and er of more team members. Fr ech sure tea, the team members are te “inet reports” of he owner. The tem “membership links denotes the data on- strets and associated content which ae wsed 1 ecard the relationships between tens and individuals sch as tam owners and team members "Ate top ofthe cain showin in FIG. 1 isa team named CEO." Tea “CHO” includes an owner, das, who the chief executive ofcer of Acme, ane to team members, Bland Chris, who epot dry to Adam acording othe comzaization's reporting chain andlor HR system. Since ‘Team “CEO” ist the op ofthe can it has no parent eam “Team "CEO" ste parent team of eams “VP. Sales” and - Operations” Also, Bo, who isthe VP. of Sales for Acai, and Chris, who isthe VP. of Operations, ae the owners of Teams “VP Sales" and “VP Operation,” tively. Among the members of Team “VP. Operations” is Dave, who is the Director of Software Development, as incted in Team “Director, Software Development.” Simi Jay, Team "Manager, Automotive Projects" and Team “Consulting Serices” identify supevisors and respective iret report Tn contrast othe static teams, the dynamic teams are not resrctad to the stricture of the reporting. chain. For example, as indicate bythe dashed srw in FIG. 1, Dave isthe owner of Team “Product Development” and George is a member, but George is the owner of Team “Quay “Assuranoe" and Dave sa member. US 7,110,988 BI 5 In any paricular implementation, parent teams may be ieetly or indirectly associated with subordinate or child ‘teams. Ia the example embodiment, data records are used to store the team definitions, and those data records include parent-team field that store identifiers forthe parent teams. $ Tn alterative embodiments, the pareat teams are ideatified indirectly. For example, parent teams may be identified by cross referencing the team owner with the lists of team, members from other teams. In any case, the data constructs and associated content which are used to record the ela tionships between teams and parent teams are Known a3 parent links. Inthe example embodiment, each ofthe static teams except for the top team is connected to the reporting bain via a respective parent lnk “The example embodiment also imposes rules regarding the relationships between dynamic Teams and regarding ‘membership in dynamic teams to help ensure that teams and goals are aligned. For example, among the restrictions imposed by’ the data control logic 12 (FG. 4) in goal ‘management system 10 are the following: 1. every dynamic team has one owner and eo or more team members, and 2. the team members of a dynamic team ar the individu als expected to work with the owner toward achieving tne oF more goals associated with the dynamic team, Ie willbe recognized by those of onary kil in the art that other restrictions or rules could be used to govern relation ships in altemative embodiments. Also, with regard to both slate and dynam teams, it should be noted thatthe tems “owner” and “team member” describe two diferent types of membership. It should also be understood thatthe term, “otal membership” includes both owners and team mem- bers. Thus, team with one owner and one team member has total membership of Wo, FIG. 1 indicates that Team “Product Development” has ‘wo team gous: “Produce software that meets all specs" and Complete software on time.” The members of Team "Prod vet Development” would be expected to help with atleast ‘one of those team goals. In the example embodiment, goal ‘management system 10 uses specific rules to contol how ‘goals are connected wit teams and otherwise managed and ‘what types of goals are supported, Those les will now be eseribed with reference to FIGS. 2 and 3. Goal management system 10 supports two types of goals ‘wam goals and team-roated goals. Team goals are goals that the owner (eg. the team leader) ereates for the team, ‘Teamtelated goals are goals that members of the team set for themselves in support of @ team goal, In the example embodiment, team-related goals may also be refered to as personal goals. An alternative embodiment also supports personal goals that individuals may’ create for themselves Without linking the personal goals to aay particular team, goals. As ilostated by the arrows in FIG. 2 relating each goal to a team andlor a person, each eam goal i linked ts 4 tear, and each team related goal i inked both fo teas and a. person, Further, personal goals according. to the alternative embodiment are ony linked to person ‘More specially, inthe example embodiment, gol man- agement system 10 imposes the following mes regarding soals: 1, every goal is either a team goal or a team-reated goal; 2. every goal has an owner, 3. cach team goa is linked to one team and is ereated and ‘managed by the owner ofthat team: 4, each team goal except for team goals ofthe top team. (Ge. each child team goal has parent goal, and that 8 s 6 parent goa slnked to the parent team ofthe team that is linked to the child team goa: 5. each chill team goal has an owner, and that owner is ‘one ofthe team member of the parent ear ofthe tea that is linked to that child team goal 6. cactteam-telated goal js Finked to one feam goal; and 7. each team-reated goal is owned by one ofthe team members of the team associatod with the team goal to \which the team-relaed goal is linked, In ation, the owner ofa goa is preferably the person who creates and manages that goal. IG. 3 illustrates how team goals ar related to teams and other goals. For example, FIG. 3 depets a team goal named “Quality” in the TEAM GOALS column, Inaccordance with, rule 3, “Quality” is linked to one team, Team “Product Development,” via the Team Owner field. In accordance with rule 4," Quality” has a parent goal of “Total Customer ‘Swooess.” and “Total Customer Success” is linked to the parent of Team “Product Development Also, 2s prrule, the owner of “Quality” is one of the team. ‘members of the parent team of Team “Product Develop- ‘meni.” That i, Dave is one of the team members of Team, “Acme” Inadditon, FIG. 3 illustrates how team-related goals are related o teams and other goals. For example, FIG. 3 depicts 4 team-related goal “Compleleness” in the TEAM-RE= LATED GOALS column. In accordance with ale 6, “Com- pleteness” is inked to one team goal (ie. “Quality. Also, accordance with rule 7, the owner of “Completeness” (ie Pat) is one ofthe team members ofthe team associated with ‘team goal "Quality." That is, Pati one ofthe team members ‘of Team “Praduct Development." The data constructs and associated content which are sed to record the relationships ‘berwoen goals and teams ae known generally s team inks, FIG, 3 also shows that personal goals according to the alternative embodiment are not inked to any other goals Refering again w FIG. 4, there is depicted w block diagram of goal management system 10 according to the ‘example embodimeat. The example embodiment imple ‘ments goal management technologies or tools as contol Tog and data constructs that encode business rules which facilitate, and enforce use of, particular oal-nanagement practices, ‘Spevifcelly, goal management system 10 features contol logic 12 which includes computer instructions for enforcing the rules deseribed herein and presenting information t0 users, as deseribed in greater detil below. For instance, those computer instrections may be programs writen inthe TAVA fanguage andor scripts written using Java Server Pages (ISP). Goal management system 10 also includes a database 16 for storing team and goal data on appropriate data storage, That data may be stored, for instance, in a relational database, such a a structured query language (SQL) database In the illustrated embodiment, database 16 and control logic 12 reside within a single data processing system 18 For example, goal management system 10- may operte within a client-server network 17, and data processing system 18 may be a server within network 17. Data pro- cessing system 18 may include one or more central process ‘ng nits (CPUs) and data storage, such a read only memory (RON), random access memory (RAM), one or more hard disk drives, CD drives, ete. The data storage devices and ‘media may also be refer to 2s computer-usable mest, Akitional computerusable medi include, without limita- ‘ion, transmission media such ws wires, radio waves, mien US 7,110,988 BI 1 waves, and other electromagnetic andlor optical caters Visual ovtpot may be presented primarily on displays of client data processing systems 19 within network 17, based fn information communicated by control logic 12. The different components for data storage, instruction process- ing, ouput presentation, et. are kaown generally a8 pro cessing resources However, numerous changes to the illustrated arange- ‘ment could easily by utilized in altemative embodiments of the invention. For example, multiple databases could be 10 ‘used, and one or more of those databases could reside onone OF mlore machines separate from the machine hosting the control logic. Similarly, components o modules of the ‘contro lgie could nun on cfferentharvare, soc as within network clients. Likewise, different types of networks, dif 1s ferent types of hardware, and diferent programming lan- _auages could be used to implement alternative embodiments of the goal management system of the preseat invention, Altematvely all operations, including the display of infor- ‘mation, could be performed in a single data processing system, For purposes of illustration, however, this detailed

Vous aimerez peut-être aussi