SLDS Best Practices Brief - National Center For Education .

2y ago
11 Views
2 Downloads
597.04 KB
5 Pages
Last View : 1m ago
Last Download : 3m ago
Upload by : Mia Martinelli
Transcription

SLDS Best Practices BriefStakeholder Communication: Tips from the StatesStates agree: Effective communication with stakeholders (districts, program offices,postsecondary education leaders, other state agencies, legislators, etc.) throughout systemdesign, development, and deployment is vital to the ultimate success of a statewidelongitudinal data system (SLDS). A group of state staff experienced with stakeholdercommunications efforts and the related challenges convened to share strategies, bestpractices, and lessons learned.The SLDS Communications Mantra: Connect. Listen. Respond. Sustain.Do:Identify and reach out to a range of key stakeholders early on.Be inclusive, but in a focused way and at appropriate times.Create realistic expectations in all communications.Form or leverage groups to lead the outreach effort.Identify key individuals as “ambassadors” and “point people.”Create and follow a clearly-defined, carefully-conceived outreach plan.Acknowledge differences among stakeholder groups and tailor your style.View communications, in part, as a change management activity.Structure meetings around very specific questions or products.Listen and be responsive to stakeholder input.Implement some early wins to gain and sustain stakeholder support.Give stakeholders credit for help with system design and enhancement.Do Not:Do not engage in large-scale, open forums.Do not ignore the political environment.Brief 1May 2011This product of the Instituteof Education Sciences (IES)SLDS Grant Program wasdeveloped with the help ofknowledgeable staff from stateeducation agencies and partnerorganizations. The informationpresented does not necessarilyrepresent the opinions of the IESSLDS Grant Program. We thankthe following people for theirvaluable contributions:Nancy CopaNaru NayakFlorida Department of EducationDeb HoldrenGeorgia Department of EducationWarren DanforthTroy WheelerIdaho Department of EducationCharles McGrewKentucky P-20 Data CollaborativeMickey GarrisonJosh KleinDoug KostyMike RebarOregon Department of EducationRobin TaylorSLDS Program, State Support TeamDo not get “techy” with most stakeholder audiences.Do not assume that everyone is in sync on system goals.Do not fail to follow through on communications promises.Do not NOT communicate.SLDS Best Practices Brief: Stakeholder CommunicationFor more information on the IESSLDS Grant Program, additionalBest Practices Briefs, or for supportwith system development, please visithttp://nces.ed.gov/programs/SLDS.1

Do:According to states, the following practices will supporteffective communication with stakeholders. (Note: Thesesuggestions do not necessarily represent the views of theIES SLDS Grant Program).Identify and reach out to a range of keystakeholders early on.Ideally, SLDS components should be designed from thestart with input from all of the intended user groups atboth the state and local levels. Identify these key stakeholdergroups early on to inform them about the project and beginto establish interest in and support for the system. Maintainclose communication with these stakeholders throughoutthe design, development and deployment phases throughdirect engagements to collect input. Hold meetings,convene focus groups1, and conduct surveys to gain inputfrom the field on initial design, ongoing development,and deliverables such as reports and tools. Hold frequentmeetings both within the state education agency (SEA),with legislative staff, and with districts. Convene meetingswith local education agencies (LEA) at least quarterly todiscuss any changes to the data system that will affect localstaff directly, as well as developments occurring at the statelevel that may not have a direct impact. These methods canbe very effective ways of engaging stakeholders, buildinga sense of collaboration between state and local staff, andcollecting information about user needs. Use other formsof communication such as emails, webinars, and a websiteto share ongoing status updates (announcements, events,grant information, contacts, etc.).Be inclusive, but in a focused way and atappropriate times.Input from a full range of stakeholder groups will promotethe ultimate utility and success of the SLDS, but too manyvoices can stifle progress and steer the project off track.Strike a balance by engaging with a manageable number ofrepresentatives from key groups and convening meetingson a schedule that matches project needs.Create realistic expectations in allcommunications.Be very clear and realistic when defining the purpose ofthe project and who it can affect. Be careful not to talkabout the project in terms of benefits to teachers and3students, and positive effects in the classroom unless it isknown for certain that the project can achieve these goals.Too many SLDS projects have promised great things forteachers when, in fact, the state ultimately fails to providethe timely data that teachers need to affect the classroom.Communicate in such a way as to “under promise and overdeliver.”Form or leverage groups to lead the outreacheffort.Task a key group (or groups) with coordination of thecommunications effort, utilizing existing groups wheneverpossible. Some successful models used by the states include: Executive group or steering committee includingleaders from across the state to develop acommunications plan, and coordinate outreach andinformation gathering efforts. Stakeholder advisory groups comprised of membersfrom a range of stakeholder groups to gatherfeedback from and speak for their respective groups.Which particular groups are represented should bedetermined by the type of initiative being addressed.For example, do you need an IT or end-user perspective(or both)? A P-20W (preK through workforce) groupof this sort may include school board sentatives,representatives from other state agencies (e.g.,labor, corrections, public assistance), policymakers,researchers, business leaders, teachers, parents, etc Association groups to engage stakeholders in-personand remotely to teach stakeholders about the system,promote the available reports and data portals, andgather user feedback.Identify key individuals as “ambassadors” and“point people.”Identify individuals to serve as champions and point peopleon the SLDS or particular system features. For instance,representatives from regions around the state (one statecalls them “ambassadors”) communicate with the SEAon a regular basis and convey messages to and from localstakeholders. It is also beneficial to identify ambassadorsfrom various peer groups. For instance, a highly regardedsuperintendent is more likely to have influence on othersuperintendents than would a school principal (and viceversa). This approach can help to 1) collect feedback fromSLDS Best Practices Brief

the “ground” to shape state plans, and 2) keep the fieldinformed about SLDS developments.Create and follow a clearly-defined,carefully-conceived outreach plan.Early on, develop a communications plan2 that clearlydefines key information about the planned outreach(e.g., audiences that should be kept informed ofSLDS development news, authors or leaders of eachcommunication activity, methods and formats ofcommunication to be used, key messages of eachcommunication, desired outcome of the communication,and the dates and frequency of communications. Also,determine when you will simply communicate about theproject (one directional) and when you will actively solicitfeedback (two directional). Be sure to identify an ownerfor the plan.Acknowledge differences among stakeholdergroups and tailor your style.Acknowledge that while some stakeholders will be receptiveto SLDS efforts, others may not. This latter group mayfeel threatened by the impending changes. The potentialneed to learn new skills, alter the way they do business,or the perception of a loss of control of the data are allcommon sources of anxiety and resistance from staff. Tryto anticipate which stakeholder groups are more likely tofit into each of these two groups (receptive or resistant)and tailor the messaging accordingly to avoid alienatingany of your stakeholders. It is also helpful to identify andaddress the distinct perspectives and interests of eachgroup. For instance, a teacher will be interested in anSLDS for different reasons than a district superintendent,so communications should be tailored to appeal to thosedistinct interests. Also, be sure to avoid technical oreducation jargon when communicating with particulargroups who may not be fluent in those languages.for the SLDS, alert users to changes in skills that may berequired for use of the data system, and suggest resourcesthat may be available. The range of skills that individualsmay need to effectively use an SLDS will vary from few tomany. The less intimidating the system is to stakeholders,the more likely they will be to accept and utilize thesystem. Therefore the more effectively the information iscommunicated to stakeholders, the less opportunity therewill be for unrealistic expectations, misunderstandings, andresistance.Structure meetings around very specificquestions or products.When meeting with stakeholders to assess needs, structurediscussions around specific questions the agency wants toanswer. These questions should be those identified by thefield as areas of need (as determined by surveys or focusgroups). Give the group specific products to respond to andkeep discussions focused, rather than starting with a blankslate. Strike a balance between presenting requirementsthat are very detailed and prescriptive and those that aretoo loosely defined. When engaging stakeholder groups,recognize that neither extreme will be ideal, so set the stageby acknowledging that reality. Even if the group decides todepart from your starting point, this approach will help tofocus the effort and generate better quality feedback.Listen and be responsive to stakeholder input.As user satisfaction will ultimately determine SLDS success,be sure to listen to stakeholder input. But don’t stopthere. Make sure stakeholders know you have heard themby responding to and acting on what they have told you(within reason). Also be sure to communicate the revisionsor changes that have been made based on stakeholders’feedback. Not only will this improve the system, it will alsostrengthen engagement and buy-in, and will help to foster acollaborative environment.3View communications, in part, as a changemanagement activity.Implement some early wins to gain and sustainstakeholder support.Creating and implementing an SLDS involves changefor many stakeholders. Good leaders use stakeholdercommunications as an important way to manage thechange process. Beyond the function of informationgathering, your communications serve to set expectationsIdentify the deliverables that can be most easily completedand tackle them for some quick wins. Provide legislators,educators and other stakeholders with not only data, butanswers to their questions. Show return on investment (e.g.,short- and long-term student earnings after graduation, total3SLDS Best Practices Brief

number of students leaving the state after graduation, timeit takes students to find jobs after graduation, high schoolfeedback reports on college success, etc.). Delivering thisvaluable information will show stakeholders the true valueof the SLDS.Give stakeholders credit for help with systemdesign and enhancement.Be sure to give credit where it is due. Acknowledgestakeholders for their input into system design anddevelopment. System success should not be attributedsolely to state education agency leadership or IT staff.Do not get “techy” with most stakeholderaudiences.When communicating or meeting with a non-technicalgroup, focus on the end user perspective of the system—the questions they want the system to answer—rather thanthe infrastructure that will make it possible to get thoseanswers. Save the technical discussions for staff who willactually need to understand that side of the system. Forinstance, legislators will not likely be the people logginginto and using the system, so save the discussion of systemaccess and use for their staff.Do Not:Do not assume that everyone is in sync onsystem goals.Based on their experiences, states warn against thefollowing common communications mistakes. (Note:These suggestions do not necessarily represent the viewsof the IES SLDS Grant Program).Regularly check in with stakeholders to make sure everyoneis on the same page when it comes to system goals anddesired outcomes. Recognize when those aspirationsevolve along the way and make sure stakeholders are awareof those changes.Do not engage in large-scale, open forums.Do not open the floor to a large group of stakeholderswith vague guidelines for discussion. The more productiveapproach may be to engage with leaders of key stakeholdergroups (superintendents associations, technical associations,school boards, principals, etc.) for focused meetings. Toomany voices can slow progress, so if you do engage a biggroup, structure the meeting around a specific set of guidingquestions or products and keep the discussion focused.Do not ignore the political environment.Political connections and support can be very beneficialwhen it comes to getting funding for system start-up andsustainability. Engage legislative and executive staff earlyon to discuss system planning; ensure that it is designed tomeet their needs and that they feel ownership of the system.Make sure legislators understand how the system will meettheir information needs and that they are convinced that itactually will. Another very successful strategy for winningpolitical support has been to encourage district staff toserve as advocates and reach out to local legislators (throughcommunications, presentations, committee hearings, etc.)to demonstrate the utility of the state system at the locallevel.4Do not fail to follow through oncommunications promises.If you do establish an expectation among stakeholders forcontinued communication, make sure you follow throughon your communications promises. Not following throughis as bad as not communicating and may be even worse.This will foster a lack of respect for the work and create anatmosphere of distrust. Even if the communicator doesn’thave anything new to report, it is still beneficial to stay intouch with stakeholders.Do not NOT communicate.Lack of communication will imperil an SLDS effort.Period.1A detailed description of an approach used by Florida to gather andprioritize user needs is available .pdf.2A sample Communications Plan template is available ntDirectory/NewDocuments/7677 communications plantemplate with instructions.doc.3For a report on how the Oregon DATA Project implemented acomprehensive strategy for stakeholder input, which ultimately decidedthe direction of the project, see the report eld.SLDS Best Practices Brief

This product of the Institute of Education Sciences (IES) SLDS Grant Program was developed with the help of . Mickey Garrison Josh Klein Doug Kosty Mike Rebar Oregon Department of Education Robin Taylor . it takes students to find jobs after graduation, high school feedback reports on college success, etc.). Delivering this

Related Documents:

help state education agencies develop and implement longitudinal data systems. These systems are intended to enhance the ability of States to efficiently and accurately manage, . Click the SLDS Portal button at the bottom of the list on the left side of the student's page. SLDS Parent Portal Guide 4 Georgia Department of Education

2.1 Switching linear dynamical systems Switching linear dynamical system models (SLDS) break down complex, nonlinear time series data into sequences of simpler, reused dynamical modes. By t-ting an SLDS to data, we not only learn a exible non-linear generative model, but also learn to parse data sequences into coherent discrete units.

Switch and Zoning Best Practices 28-30 2. IP SAN Best Practices 30-32 3. RAID Group Best Practices 32-34 4. HBA Tuning 34-38 5. Hot Sparing Best Practices 38-39 6. Optimizing Cache 39 7. Vault Drive Best Practices 40 8. Virtual Provisioning Best Practices 40-43 9. Drive

The Global Association for Contact Center Best Practices & Networking www.ContactCenterWorld.com THE BEST PRACTICE SERIES Nov 11-15, 2013 Benchmarking, Networking & Best Practices IN THE CONTACT CENTER WORLD TOP RANKING PERFORMERS BEST PRACTICES CONFERENCE & AWARDS WORLD'S BEST LAS VEGAS . Kansas City Call Center

Within each category, the Election Security Best Practices Guide separates the recommendations into two levels according to their criticality to help Election Authorities prioritize the implementation of the practices: (1) Priority Best Practices and (2) Standard Best Practices. Priority Best Practices are urgently critical and form the .

The Project Brief can take two forms: A letter Brief may be used for projects less than 100,000 (total cost including GST and fees). Full Brief utilising a project specific brief with this Basic Brief. The Project Brief in its dra

VMware ESX Host Best Practices for Citrix XenApp –Provides proven VMware best practices for vSphere hosts running XenApp workloads. Includes guidance in the areas of CPU, memory, storage, and networking. Citrix XenApp on vSphere Best Practices – Deploying Citrix XenApp on vSphere requires that proven best practices for the XenApp application continue to be followed. The focus in this section is on

AMERICAN BOARD OF RADIOLOGY, ) ) CLASS ACTION ) Trial by Jury Demanded Defendant. ) CLASS ACTION COMPLAINT Plaintiff Sadhish K. Siva, (“Plaintiff”), for his Complaint against Defendant American Board of Radiology (“ABR” or “Defendant”) hereby alleges as follows: INTRODUCTION 1. This case is about ABR’s illegal and anti-competitive conduct in the market for initial board .