Digital Standards Re'form { ; con'form; sosighettetull, sewshul (fails), sewsighette T-shirtshort (fail) } , consulting topics, concerning which Patrick Lee Cheatham has strong interest
A summary of topics for reading at option, by any interested persons staffing various Microsoft divisions, and divisions of other company entities having computer / device / internet very active roles
Office 365, Windows OS, Visual Studio IDE, and the I.D.E.A.S. Team are Microsoft divisions likely most interested in in-house standards initiatives and reforms
My main skillset and background readiness, plus my main motivation to reform internet / device / computer paradigms, leveraging and improving on the better, and superseding poor standards, is summed up in a small position essay on new reform standards potentials.
Next is a text-pallet of content I have posted on Substack and LinkedIn, which presents typical sets of guiding criteria I use for good standards internet/device-wise. I typically have a knack for about 3-8 out of 10 good success/fail ratio/rate on feasibility and practical scalability and sustainability of my ideas, with allowance for my reaction options upon critique and outside perspective to hone ideas performed by essential and crucial implicit peer review, from layperson to expert to child. My idea creation style and skills I could provide as consultant to Office 365, Operating Systems, and IDE Development personnel especially. I wrote: "Proprietary standards ownership is not for hardline compliance enforcement. Instead, it involves significant staffing and reason, motivation, involvement to ensure [1] standards are optional [2] modification or augmentation of standards is only as the standard itself specifies, to meet "{realm-issue} standards proficient" certification by {entity} (as Microsoft, feasibly, and/or other mainstay global internet/device entities, also). Staffing enough in personnel to review many wares (internet implementations and software titles) and ways for "{realm} standards proficient" certification, "{realm} standards adept" certification and "{realm} standards excellence in implementation" certification. The first level "proficient" should not be a service for which entities must pay for such certification but would be a power of {entity} to release opinion that some wares or ways on the internet "do not meet {entity} {realm} standards proficiency minimums". Thus, the power to foster and lead globally is by negation, by reputation, and for 3 levels of certification. Level 1 proficient is assumed by default and by grace permissive, unless flagged otherwise, and initially mild as notice of feasible and potential improvement, especially as new and unfamiliar standards are becoming established and better known of." I posted: Global Conveyances (email / messaging / posts / comments) Proprietary Standards* - *Such Standards are minimum limits, instead of visionary goals - at patricklcheatham.substack.com.
I applied for:
Senior Product Designer in Redmond, Washington, United States, Design & Creative at Microsoft
If formal structured employment by Microsoft is other than most well suited on part of both parties considered, then a somewhat more tailored (and much less payroll costly for Microsoft) contract consulting pay-on-fruition role by me, could allow for similar progress relooking tech-chronological stacks of ways, means, standards, file-formats of 1980-2020.
I've applied to Microsoft IDEAS team, as a means of introduction, for possible consulting opportunities, or for contractual affiliation and association with fulfillment criteria similar to or meeting Microsoft employment specifications.
In my application of yesterday I did not append or annotate the existence of a product design portfolio, yet talon38filemedia.com, patrickleecheatham.medium.com, and patricklcheatham.substack.com, together provide ample links and presentations on my design works, presently. I've been actively of varied contact methods prompting Microsoft personnel who review various inputs on suggestions and submissions, in various persistent ways, for several days while approaching mid-June 2025 - to spread a bit more widely than minimum of one, several discoverable copies of my text-pallets or idea tidbits, which I consider of some merit and better to err toward more copies on more sites, pages, or services, in the spirit of human domain idea dissemination. Thus, I’ve shared and posted and linked much and often on these topics.
I’ve posted and shared via Substack, LinkedIn, Feedback Hub, Instagram, X.com, Microsoft Partner Center, and Microsoft Careers Job application.
I am currently pursuing either stimulating, discussing, consulting on, drafting methods toward, or/or performing formal codification for Microsoft or other internet / devices / computer company entities, concerning their working implementations of minimum standards definitions, handling procedures, certification contingencies, and equitable commerce-style promulgation and open competition attitudes toward fostering and evolving such standards as mainstay daily and monthly fare, setup and readied, with the staying power to sustain such operations and readied roles, for years and decades of futures.
I am skilled and aware on trappings and pitfalls associated with new idea generation, and revision of existing norms in digital and human processes. Ideas have factors, they have tie-ins, and they have by nature great mis-aim, miscue and error (which is as should be) until after much peer review refines them and seasons them.
For Office 365 specifically, as a very short and incomplete sampling of basis idea-styles, I jot herein and next, an unrefined list of relatable and familiar features that could change by standard, to indicate potentials and style: [1] revamping email format / process with more fields, recipient list listing and delivery payload field capacity, plus POP-IMAP replacements, [2] reforms at To Do wordings of meaning and structural merit to the application, toward ‘aim’/’goal’ date/time/delay, etc. instead of the word ‘due’, [3] major paradigm shifts in "conveyances" [archaically, to some extent and in some opinion-latitude - emails / messages / posts / comments - referred to better as ‘conveyances’ in general element type] sent to/from, [4] personal productivity category list sets crafted thoughtfully by realm and featuring both inclusive-enough in total set of broad coverage and with granularity between single category items in the set list not dual or overlapping but blatantly indicative of pertaining category, by well-crafted selection of category titles and comparative interrelationship plus delineations intrinsic to category wordings of good differ but similar overall realm, [5] archive and retention file formats and process fields of lusher and more granular structure and tiering within groups, [6] radical revamping of file explorer access UI and mouse/keystroke flow, plus font / layout / size and white / negative / contrast "space" [margin/padding] explorative for effect new creations, for better depiction in-application of ‘conveyance content’, and new ideas for [7] tool ribbon mainstays for classic Office apps.
I possess interest and passion enough for these topics, as well as awareness and realization of these topics readied and timely potentials very existent presently, to the extent that I selected as course of wording terminology to proceed and couch these posts and submissions as formally interpretable as acting as tentative proposals of mine, for counterproposal or re-proposal, to those Microsoft divisions mentioned earlier and above at the beginning of this particular post.
As additional depth of Office experience I have to my background, in my former engineering, pilot and military employment roles as airframe propulsion integration engineer and then later as instructor pilot and evaluator pilot, I used Word especially much with table techniques I pioneered, for producing some novel and subtly tweaked word document template designs. I also did similar with the Access Jet database engine in decades ago popularity of Crystal Reports usage with ADO, before QuickBasic and Visual Basic IDE standards and event driven standards made their way into C# MSIL design as of VS 2002, gladly more concise and smoothly quick-typed than Visual Basic too-long keywords, while preserving excellent event driven presentation in IDE from VB.
