[wg-review] 9. [DNSO Quality] Register.com Position

["Laura Fleisher" <lfleisher@register.com>]

Register.com Position - DNSO Quality

We at register.com commend the DNSO for striving to improve the quality of
the organization.  A key issue for the DNSO's focus should be transparency
and accountability in the organization's processes. More transparency, which
includes thorough and effective dissemination of information, would advance
the goals of the DNSO by encouraging broader participation in DNSO
initiatives, creating a greater sense of legitimacy among the DNSO
membership for its actions, and offering well founded policies. Three areas
that would benefit most are projects, budget, and leadership activities.

1. Projects:
Projects undertaken by DNSO working groups and task forces have been most
effective when the goals and processes of the projects are clearly defined.
For instance, a project plan or charter, such as the one posted for Working
Group D (http://www.dnso.org/dnso/notes/19990723.NCwgd.html), establishes a
foundation on which individuals and organizations may plan their involvement
in projects. By informing interested parties of the objectives of the
project and the projected time schedule for key steps in the process, these
parties are able to easily follow the progress of the project, participate
as they feel necessary, and understand how their participation will affect
the process.

Project plans should be published on the website at the outset of a project
and progress summaries should be promptly updated on the website.  This is
in addition to their mention on working group discussion lists. If
interested parties have to dig through email lists to get to key pieces of
information, many lose interest and/or trust in the project. Given that,
register.com would offer the following specific suggestions for future
projects:
A. All key documents regarding goals, decisions, and plans for the project
should be published on the website in an easily accessible manner.
B. A clear goals and proposed methods document should be published at the
outset of each project.
C. A detailed timeline of project steps should be published with the goal
document.
D. Realistic timeframes that allow sufficient time for comment and response
at each stage of the process (e.g. a) confirm project goals b) confirm
project method c) first round of proposals…).

2. Budget
Transparency in the budget process would lend additional credibility to the
DNSO, as well as make future voluntary contributions to the budget more
likely. Constituencies would be more enthusiastic about their involvement if
they had a clearer idea how dues were being allocated. Currently, budget
information is posted within the minutes of NC meetings and teleconferences,
as seen in the Scribe's Notes from the NC meeting on November 14, 2000 in
Los Angeles (http://www.dnso.org/dnso/notes/20001114.NCmdr-minutes.html).
While the information presented in such reports is important, it does not
contain sufficient detail nor does it allow an outside reader to know what
is the final or formal budget of the DNSO.  A separate, detailed report
would allow constituency members and other interested parties to gain a
better understanding of the DNSO's work. To achieve these objectives,
register.com would like to recommend that:
A. A standing format be developed for reporting DNSO budget information,
including sources of income, itemized expenses, and other relevant
information.
B. This information be presented in an accessible format on the DNSO
website.

3. Leadership Activities
The NC representatives are the public face of the DNSO and have worked hard
to achieve highest level of credibility for the organization. The DNSO
leadership would build upon this spirit of openness by disclosing their
current employment and consulting arrangements and experience as part of
their background materials. The website can be revised to provide such
biographical and professional information


--
This message was passed to you via the wg-review@dnso.org list.
Send mail to majordomo@dnso.org to unsubscribe
("unsubscribe wg-review" in the body of the message).
Archives at http://www.dnso.org/archives.html